fix(16054): Normalize usage of types | replace ReactNodeLike with ReactNode #16465
Conversation
This file contains 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
✅ Deploy Preview for v11-carbon-react ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
LGTM!! |
riddhybansal
approved these changes
May 14, 2024
guidari
approved these changes
May 15, 2024
Merged
via the queue into
carbon-design-system:main
with commit May 15, 2024
0d27e71
20 checks passed
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes #16459 -
Closes #16460
Closes #16461
Closes #16462
Closes #16463
Closes #16464
This PR fixes inconsistencies and Normalizes the usage of types
ReactNodeandReactNodeLikein components .Now the component props accept ReactNode instead of ReactNodeLike
Changelog
Changed from
ReactNodeLiketoReactNodeTesting / Reviewing
This should not require any visual/functional testing, please verification if the existing functionality is intact.