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
{{ message }}
This repository has been archived by the owner on Mar 15, 2024. It is now read-only.
In our design system (storybook), without the Polymorphic, called as:
type ButtonComponent = Polymorphic.ForwardRefComponent<'button', CustomProps>;
We're losing the "autocomplete" for the component when we import it somewhere.
We want to remove the Polymorphic and use some native alternative from react...
what do you suggest?
Currently, when we remove the Polymorthic we really loose the autocomplete, the props that the component can receive ...
e.g:
<Button ???? />
after button, when I do command + space do not show the possible props to use... if we remove the Polymorthic usage.
The text was updated successfully, but these errors were encountered:
We have deprecated the polymorphic package in favour of the asChild prop so we don't really use it anymore.
That said if you can provide a sandbox reproducing your issue, perhaps we can still try to help?
Basically we moved away from the as prop as it brings polymorphism with it which makes everything more complex, especially type-wise. This new approach doesn't have any of these caveats and so overall performance is way better.
In our design system (storybook), without the Polymorphic, called as:
We're losing the "autocomplete" for the component when we import it somewhere.
We want to remove the Polymorphic and use some native alternative from react...
what do you suggest?
Currently, when we remove the Polymorthic we really loose the autocomplete, the props that the component can receive ...
e.g:
after button, when I do command + space do not show the possible props to use... if we remove the Polymorthic usage.
The text was updated successfully, but these errors were encountered: