-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Differences in Preact.Children API and React.Children API #2644
Labels
Comments
deleonio
added a commit
to deleonio/preact
that referenced
this issue
Jul 22, 2020
deleonio
pushed a commit
to deleonio/preact
that referenced
this issue
Jul 28, 2020
deleonio
added a commit
to deleonio/preact
that referenced
this issue
Sep 29, 2020
Is this issue still open? |
Yes. It's unlikely to be fixed, as no issues have ever been opened citing this as a real-world compatibility issue. |
Does this mean I can't work on it? I saw the "beginner-friendly" tag. |
ParSal123
added a commit
to ParSal123/preact
that referenced
this issue
Jan 8, 2023
React's children api map function supports a "context" argument that we don't. See preactjs#2644.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey friends!
I noticed a small difference in how
React.Children
is implemented betweenpreact/compat
and React.preact/compat
children: https://github.com/preactjs/preact/blob/master/compat/src/Children.js#L3react
children: https://github.com/facebook/react/blob/121af3143c7164a196420b080cb31d0ef07d5dff/packages/react/src/ReactChildren.js#L223The different here being that the React implementation allows for a
context
arg, while thepreact/compat
version does not. While it's easily fixable on our end, it seemed like the kind of thing which might lead to incompatibilities in library code.The text was updated successfully, but these errors were encountered: