You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
mj12albert
changed the title
[InputBase][material-next] slotProps accepts sx type
[InputBase][material-next] InputBase slotProps accepts sx type
Nov 2, 2023
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't Material Next have slotProps types similar to Joy UI, as shown here? This will account for the sx type in each component's slotProps and thus we won't need to add it separately.
Though we could probably modify SlotComponentProps to accept another type argument to handle this later
I meant to create a distinct type for Material Next, similar to Joy UI. This type can utilize Base UI's SlotComponentProps but also includes sx props. However, let's address this later.
This file contains hidden or 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
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.
Part of #38372
This PR ports the fix in #39569 to
material-next