Move isAttributeNameSafe to DOMProperty #11802
Merged
Conversation
This file contains 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
nhunzaker
reviewed
Dec 7, 2017
| warning(false, 'Invalid attribute name: `%s`', attributeName); | ||
| } | ||
| return false; | ||
| } |
There was a problem hiding this comment.
Any reason not to use a Set?
There was a problem hiding this comment.
This might be a good place to use it, but only with a benchmark run confirming it :-)
nhunzaker
approved these changes
Dec 7, 2017
|
No bundle size changes? |
|
Nvm both server and client use DOMProperty anyway. |
gaearon
approved these changes
Dec 8, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Deduping
isAttributeNameSafe.DOMPropertyfeels like the best place forisAttributeNameSafesince: