-
-
Notifications
You must be signed in to change notification settings - Fork 8.6k
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
fix(runtime-dom): map kebab attributes to camelCase props (fix #13055) #13085
Open
vonBrax
wants to merge
8
commits into
vuejs:main
Choose a base branch
from
vonBrax:main
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
9cb07e6
fix(runtime-dom): check for camel-case element prop
vonBrax 5b21129
test: add kebab to camel prop tests
vonBrax 4b473d2
Merge branch 'main' into main
edison1105 489d285
perf(runtime-dom): cache element prop key
vonBrax 2e8c775
Merge branch 'main' of github-private:vonBrax/vuejs-core
vonBrax b4bdb6d
Merge branch 'vuejs:main' into main
vonBrax d639feb
Revert "perf(runtime-dom): cache element prop key"
vonBrax 74d74d7
chore: Merge branch 'main' of github-private:vonBrax/vuejs-core
vonBrax File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we can cache camelKey on el like this:
patchProp
changes as followsCall
camelize
only once, checkin
only onceThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, we can cache the check result in the element itself. I would just like to point that there are 2 situations where we need to perform the check: for
.prop
bindings and at the endshouldSetAsProp
.For
.prop
bindings, check would always be performed and only once.But if we are coming from
shouldSetAsProp
, to also avoid performing thein
check when we don't need to, I would also need to add the$${key}
property on the places whereshouldSetAsProp
would return true - or alternatively set its default value in the top of the function.I have a question though: is it possible that
el
would already have a property with the name we are setting ($${key}
)? Should we actually add a check for that and what to do if it already exists?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We could use a
symbol
as key too... either to set directly the value of the current prop being set (would get overwritten by every new attribute being set and not cached across renders) or use it to create an object where properties could then be referenced by their specific key and thus caching the results. Or we leave it as you suggested above. Thoughts?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We just need to use a key that is as unlikely to duplicate as possible, such as
$_v_prop_${key}
or symbol as key.