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
A lot of params for the various types of inputs, in the v4.0 dont allow to pass undefined anymore, to be able to manage some of the params as options in a parent component for example. Its for some specific reason? Or can we put back the undefined to use default behaviours?
Examples:
Button -> gradient, rightIcon with undefined
Select -> itemComponent as undefined
Multi-Select -> valueComponent, itemComponent as undefined
In which browser did the problem occur
all
If possible, please include a link to a codesandbox with the reproduced problem
No response
Do you know how to fix the issue
Yes
Are you willing to participate in fixing this issue and create a pull request with the fix
Yes
Possible fix
Analyse the prop to see if its undefined before trying to use it and callback for default.
The text was updated successfully, but these errors were encountered:
What package has an issue
@mantine/core
Describe the bug
A lot of params for the various types of inputs, in the v4.0 dont allow to pass undefined anymore, to be able to manage some of the params as options in a parent component for example. Its for some specific reason? Or can we put back the undefined to use default behaviours?
Examples:
Button -> gradient, rightIcon with undefined
Select -> itemComponent as undefined
Multi-Select -> valueComponent, itemComponent as undefined
In which browser did the problem occur
all
If possible, please include a link to a codesandbox with the reproduced problem
No response
Do you know how to fix the issue
Yes
Are you willing to participate in fixing this issue and create a pull request with the fix
Yes
Possible fix
Analyse the prop to see if its undefined before trying to use it and callback for default.
The text was updated successfully, but these errors were encountered: