prefer @folio/stripes exports to private paths when importing components
Description
CSP Request Details
None
CSP Rejection Details
None
Potential Workaround
None
relates to
Checklist
hideTestRail: Results
Activity
Show:

Khalilah Gambrell October 17, 2022 at 3:46 PM
- all of the linked stories are closed. So I am closing this one.
Done
Details
Assignee
UnassignedUnassignedReporter
Zak BurkeZak BurkePriority
TBDSprint
NoneDevelopment Team
Stripes ForceTestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Unassigned
UnassignedReporter
Priority
Sprint
None
Development Team
Stripes Force
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created May 26, 2021 at 7:07 PM
Updated September 5, 2023 at 2:59 PM
Resolved October 17, 2022 at 3:46 PM
TestRail: Cases
TestRail: Runs
Overview: component imports should happen through the
@folio/stripes/${repo}
namespace rather than directly via the repo's private path. e.g. preferinstead of
An app doesn’t depend directly on
@folio/stripes-thing
; it depends on@folio/stripes
. No changes are required in an app app aside from fixing the import path. It’s just a clean-up task, asking apps to use stripes-* libs via their public interfaces (which are guaranteed to remain constant across minor and patch releases) instead of their private paths (which are not).