-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Little clarification on buffer.type #629
Labels
Comments
Yes, I agree. Thanks for catching this. Can you please open a PR into the |
Spec mentions also |
Yes, please. |
@pjcozzi Could you label this issue as |
Yes, labeled. |
Updated in #826 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Some time ago (#141, #233),
text
was added as a valid value forbuffer.type
enum for future compression support.At the moment (1.0-1.0.1), spec doesn't define any compression method. Nor it defines what to do with assets with
buffer.type: "text"
.Maybe it will be reasonable to remove
text
from valid values enum forbuffer.type
for 1.0.1, and propose it later via specific compression extension?The text was updated successfully, but these errors were encountered: