This repository was archived by the owner on Jun 15, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 38
Fix the usage of spreadProps without any other props #645
Merged
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,25 @@ | ||
@@jsxConfig({version: 4, mode: "classic"}) | ||
// Error: spreadProps should be first in order than other props | ||
// let c0 = <A x="x" {...p} /> | ||
|
||
// Error: multiple spreadProps not allowed | ||
// let c0 = <A x="x" {...p0} {...p1} /> | ||
|
||
// only spread props | ||
let c1 = React.createElement(A.make, p) | ||
|
||
// reversed order | ||
let c2 = React.createElement(A.make, {...p, x: "x"}) | ||
|
||
@@jsxConfig({version: 4, mode: "automatic"}) | ||
// Error: spreadProps should be first in order than other props | ||
// let c0 = <A x="x" {...p} /> | ||
|
||
// Error: multiple spreadProps not allowed | ||
// let c0 = <A x="x" {...p0} {...p1} /> | ||
|
||
// only spread props | ||
let c1 = React.jsx(A.make, p) | ||
|
||
// reversed order | ||
let c2 = React.jsx(A.make, {...p, x: "x"}) |
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,25 @@ | ||
@@jsxConfig({version:4, mode: "classic"}) | ||
// Error: spreadProps should be first in order than other props | ||
// let c0 = <A x="x" {...p} /> | ||
|
||
// Error: multiple spreadProps not allowed | ||
// let c0 = <A x="x" {...p0} {...p1} /> | ||
|
||
// only spread props | ||
let c1 = <A {...p} /> | ||
|
||
// reversed order | ||
let c2 = <A {...p} x="x" /> | ||
|
||
@@jsxConfig({version:4, mode: "automatic"}) | ||
// Error: spreadProps should be first in order than other props | ||
// let c0 = <A x="x" {...p} /> | ||
|
||
// Error: multiple spreadProps not allowed | ||
// let c0 = <A x="x" {...p0} {...p1} /> | ||
|
||
// only spread props | ||
let c1 = <A {...p} /> | ||
|
||
// reversed order | ||
let c2 = <A {...p} x="x" /> |
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.
Looking at the generated output, perhaps this should also be the only order allowed, and the first example, in the other order, should be an error?
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.
I think we need to describe the spec of how the spread props will work compared to the js. In js, always the latter one has a priority which means order does matter. But in v4 spread props, independent props always have a priority.
How about allowing reversed order only? The semantic seems matching to the js output.
Or, describing on the spec that each independent prop will be updated at the end regardless of order.
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.
Exactly. Allowing reverse only seems natural. And avoids confusion if there's only one way.
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.
One thing came to my mind, maybe I think I can extract the (label, expression) list from arguments and label declaration in spread prop. then I can reduce it to the single record expression. I’ll give it a try.
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.
Ah..I confused. Never mind the reduce thing,
p
is a just Lident not Pexp_record.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.
afdd64b