Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AIP-143: revisit the naming of "mime_type" #131

Open
toumorokoshi opened this issue Mar 14, 2024 · 0 comments
Open

AIP-143: revisit the naming of "mime_type" #131

toumorokoshi opened this issue Mar 14, 2024 · 0 comments
Milestone

Comments

@toumorokoshi
Copy link
Member

          I'm not entirely sure. I guess since HTTP calls is content-type, we should follow suit?

https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Type

I don't think we should be constrained by legacy - if there's backwards-incompatible changes we need to introduce let's just provide migration guides. I'd rather minimize the number of suboptimal changes we make for legacy, but open to opinions!

Originally posted by @toumorokoshi in #90 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant