This repository was archived by the owner on Nov 6, 2019. It is now read-only.
Use camel case for element attribute and event names#282
Open
gnestor wants to merge 2 commits intophosphorjs:masterfrom
Open
Use camel case for element attribute and event names#282gnestor wants to merge 2 commits intophosphorjs:masterfrom
gnestor wants to merge 2 commits intophosphorjs:masterfrom
Conversation
Contributor
|
Can we allow phosphor to accept the lowercase and react style names to avoid forcing a 2.0 release? |
Member
|
Yeah, we're gonna have to do something like that. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Broken out from #281
This will allow phosphor’s virtualdom to support rendering React functional/stateless components.
To do: