Skip to content

Conversation

@safwansamsudeen
Copy link

This is how the guide looks right now:
image

I removed the extra ?. - is it necessary?

@changeset-bot
Copy link

changeset-bot bot commented Oct 24, 2024

⚠️ No Changeset found

Latest commit: ffabc14

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@leonardsimonse
Copy link

The docs are correct in this instance. children is of type 'any', so this notation is required. It ensures children is not null or undefined. children might not always be passed as a prop and the component should not crash in that instance.

@benmccann benmccann changed the title fix: correct typo in migration guide docs: fix typo in migration guide Oct 24, 2024
@benmccann benmccann closed this Oct 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants