-
Notifications
You must be signed in to change notification settings - Fork 32
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
Attributes divergence #34
Comments
I'm not comfortable with only forwarding this through the whole language if only 1 attribute is supported ( E.g. Browsers adding things like |
As we think about the future we’re going have files that need to be interpreted in multiple environments and we expect those environments to change over time (like the browser adding If we assume that only a single property is important we aren’t future proofing very well. It should be safer to just forward along all the properties and assume arbitrary properties may be present and could be important to someone at some point in the future. |
Ultimately, I think the main tool we have available for ensuring compatibility across environments is making normative requirements in the specification. The current draft specification defines requirements for |
One of the concerns with arbitrary attributes it's a possible divergence in an already divergent ecosystem (tooling configuration are not shared for instance).
For the Babel implementation the plan would be to make it available, via the Babel AST, to plugins. Plugin authors would be free to define their own attributes.
type
attribute? Maybe Use general key-value syntax, or a single string? #12 would make more sense then.The text was updated successfully, but these errors were encountered: