Uploaded image for project: 'Stripes'
  1. Stripes
  2. STRIPES-751

prefer @folio/stripes exports to private paths when importing components

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • TBD
    • Resolution: Done
    • None
    • None
    • None
    • None
    • stripes-force 151
    • Stripes Force

    Description

      Overview: component imports should happen through the @folio/stripes/${repo} namespace rather than directly via the repo's private path. e.g. prefer

      import LocationSelection from '@folio/stripes/smart-components/LocationSelection';
      

      instead of

      import LocationSelection from '@folio/stripes-smart-components/lib/LocationSelection';
      

      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).

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

                Unassigned Unassigned
                zburke Zak_Burke
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases