LG-4724: Export prop types which are already wrapped in the polymorphic types (re-created) #2613
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
🦋 Changeset detectedLatest commit: 9ea67d3 The changes in this PR will be included in the next version bump. This PR includes changesets to release 5 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
6 tasks
|
Size Change: 0 B Total Size: 1.4 MB ℹ️ View Unchanged
|
shaneeza
approved these changes
Jan 7, 2025
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.
This PR is a re-creation of #2609 (using a branch on the repo instead of from my personal fork).
✍️ Proposed changes
I went through the codebase to find uses of the "polymorphic" types and replicated the pattern already established for the
SubMenucomponent:*Propstype name with "Internal".PolymorphicPropsorInferredPolymorphicProps(depending on which was used by the implementation of the component).I'm marking this as a patch, since it's extending the existing prop types and therefore shouldn't cause downstream breakage. If a consumer is wrapping these types already this should be a no-op.
🎟 Jira ticket: LG-4724
✅ Checklist
For bug fixes, new features & breaking changes
yarn changesetand documented my changesFor new components
🧪 How to test changes