[@mantine/core] Fix types for components that forward ref #2505
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
HorizontalSectionProps and PrismProps should not contain ref in their props
|
Thanks! |
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 #2504
This PR refactors the utility type
ForwardRefWithStaticComponentsdefined insrc/mantine-utils/src/ForwardRefWithStaticComponents.tsin order to build a final type which match what forwardRef returns plus the static properties we want to expose.Changing
ForwardRefWithStaticComponentshas helped to find that at least 15 components were affected with missing ref attribute in their typeNote that prettier had to be updated due to this issue prettier/prettier#12640