We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Right now many consumers use our utils functions. They do so because the utils are available, but not via a nice path.
For example this search (employees only) shows a few callsites of people importing ForwardRefComponent and useIsomorphicLayoutEffect.
ForwardRefComponent
useIsomorphicLayoutEffect
We expose utils as a proper path, with re-exports, so one can write, for example:
utils
import type {ForwardRefComponent} from '@primer/react/utils'
as opposed to the current:
import type {ForwardRefComponent} from '@primer/react/lib-esm/utils/polymorphic'
The text was updated successfully, but these errors were encountered:
keithamus
Successfully merging a pull request may close this issue.
Problem statement
Right now many consumers use our utils functions. They do so because the utils are available, but not via a nice path.
For example this search (employees only) shows a few callsites of people importing
ForwardRefComponent
anduseIsomorphicLayoutEffect
.Proposed solution
We expose
utils
as a proper path, with re-exports, so one can write, for example:as opposed to the current:
The text was updated successfully, but these errors were encountered: