-
-
Notifications
You must be signed in to change notification settings - Fork 497
Fix #1048: Allow rest props to override lazyProps data properties #1071
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
Closed
erikras-dinesh-agent
wants to merge
1
commit into
main
from
fix/issue-1048-allow-input-prop-override
+72
−9
Closed
Changes from all commits
Commits
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 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
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
Oops, something went wrong.
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.
🧩 Analysis chain
🌐 Web query:
JavaScript object rest spread syntax symbol keys enumerable properties💡 Result:
{ ...obj }) copies only the source’s own, enumerable properties into the new object (it’s a shallow copy; it does not copy non-enumerable properties or anything from the prototype chain). EnumerableSymbol-keyed properties are included (non-enumerable symbol properties are not). [1][2][3]const { a, ...rest } = obj) collects the remaining own, enumerable property keys (i.e., what’s left after the picked properties), and this likewise includes enumerable symbol keys. [4][2]Example:
(Enumerability of symbol properties matters specifically for
Object.assign()and object spread.) [3][2]Sources: [1] MDN Spread syntax, [2] MDN Enumerability and ownership of properties, [3] MDN
propertyIsEnumerable(), [4] MDN Destructuring assignment (rest in object destructuring).🌐 Web query:
Object.assign copy symbol keys properties💡 Result:
Object.assign(target, ...sources)copies own, enumerable properties from each source ontotarget, and it copies both string-keyed and symbol-keyed properties (i.e., enumerableSymbolproperties are included). It does not copy properties from the prototype chain or any non-enumerable properties. It performs assignment via[[Get]]on the source and[[Set]]on the target (so getters/setters can run). [1] [2]🌐 Web query:
for..in loop symbol keys iteration JavaScript💡 Result:
for...indoes not iterate Symbol-keyed properties—it only visits enumerable string property keys (and it also ignores Symbol keys even if they’re enumerable). [1]To iterate Symbol keys, use one of these:
Only Symbol keys (own properties)
Object.getOwnPropertySymbols()returns an array of an object’s own Symbol properties. [2]All own keys (strings + symbols; enumerable + non-enumerable)
Reflect.ownKeys()returns all own property keys, including both strings and symbols. [3]MDN also explicitly notes Symbols aren’t enumerable in
for...in, and points toObject.getOwnPropertySymbols()as the way to retrieve them. [4]Symbol‑keyed rest props are dropped with
for..in.for..inskips symbol keys entirely, which diverges from object‑rest /Object.assignsemantics that include enumerable symbols. Consider iterating withReflect.ownKeys()instead and apply the same change to the other two merge loops.🔧 Suggested fix (apply similarly in the other two loops)
📝 Committable suggestion
🤖 Prompt for AI Agents