Skip to content
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

Add explicit children prop #268

Merged
merged 1 commit into from
Apr 22, 2022
Merged

Add explicit children prop #268

merged 1 commit into from
Apr 22, 2022

Conversation

nickjs
Copy link
Contributor

@nickjs nickjs commented Apr 21, 2022

Hi!

@types/react has been updated for react 18 to no longer include an implicit children prop on every Component. This means <FlipMove> is no longer usable with the latest react typings because you must pass children to <FlipMove> but TypeScript thinks the <FlipMove> component doesn't accept any children.

This PR adds an explicit children prop to the typings including a doc comment.

Thanks!

`@types/react` has been updated for react 18 to no longer include an implicit `children` prop on every `Component`. This means `<FlipMove>` is no longer usable with the latest react typings because you must pass `children` to `<FlipMove>` but TypeScript thinks the `<FlipMove>` component doesn't accept any `children`.
Copy link
Collaborator

@xcv58 xcv58 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm!

@xcv58 xcv58 merged commit 9f17f68 into joshwcomeau:master Apr 22, 2022
@nickjs
Copy link
Contributor Author

nickjs commented Apr 22, 2022

Thanks @xcv58!

@JakeThurman
Copy link

JakeThurman commented Nov 3, 2022

@xcv58 Can you create a release for this change? I am running into this issue with the latest version since it doesn't include this change

@xcv58
Copy link
Collaborator

xcv58 commented Nov 4, 2022

@xcv58 Can you create a release for this change? I am running into this issue with the latest version since it doesn't include this change

Sorry I don't have that permission to do the release, waiting for this #233 (comment)

@JakeThurman
Copy link

@xcv58 Can you create a release for this change? I am running into this issue with the latest version since it doesn't include this change

Sorry I don't have that permission to do the release, waiting for this #233 (comment)

Saw that after posting! Thanks for taking the time to reply.

This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants