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
There are a few places where PF components are being imported from different locations.
Most places, i've noticed components are imported from @patternfly/react-core/dist/dynamic...
Some places, components are import using a different pattern, like @patternfly/react-core like here.
Unless there's an architectural reason to do otherwise, I think it's likely easiest to import all PF components from @patternfly/react-core and let the build config determine resolve the import the way it's set up to.
If you need to use a deprecated component - you'd import them from @patternfly/react-core/deprecated
But PF does provide a non-deprecated solution for every deprecated component - feel free to reach out if those solutions are not working for findable for any reason.
The text was updated successfully, but these errors were encountered:
There are a few places where PF components are being imported from different locations.
Most places, i've noticed components are imported from
@patternfly/react-core/dist/dynamic...
Some places, components are import using a different pattern, like
@patternfly/react-core
like here.Unless there's an architectural reason to do otherwise, I think it's likely easiest to import all PF components from
@patternfly/react-core
and let the build config determine resolve the import the way it's set up to.If you need to use a deprecated component - you'd import them from
@patternfly/react-core/deprecated
But PF does provide a non-deprecated solution for every deprecated component - feel free to reach out if those solutions are not working for findable for any reason.
The text was updated successfully, but these errors were encountered: