Uploaded image for project: 'UX Product'
  1. UX Product
  2. UXPROD-2889

Split stripes-core

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: In Progress (View Workflow)
    • Priority: P3
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Template:
      UXPROD features
    • Development Team:
      Stripes Force
    • Calculated Total Rank:
      0
    • PO Rank:
      0
    • PO Ranking Note:
      Holly set the PO Rank to the default (zero) for now so the PO's features sort properly in the filter.

      Description

      Our current stripes-core setup bundles a lot of parts together:

      • stripes-cli
      • webpack
      • stripes-config (okapi getModule)
      • permissions, contexts, providers used by ui modules
      • testing context

      This is currently causing some limitations. The most recent issues are:

      We should consider splitting it up. After working on FOLIO-2673 for a bit this structure came to my mind:

      Static - possible to package in vendor DLL:

      1. 3rd party libs (react, redux, etc)
      2. stripes vendor (all stripes-* modules) this includes stripes-core (permissions, stripesConnect, AppIcon, IntlConsumer, providers, webpack and basically all imports from stripes-core used currently from various ui-modules).

      Dynamic - build based on a given stripes.config.js:

      1. stripes-config (includes okapi config, branding, etc) (possible to build into a separate webpack entry so it can be swapped without full rebuild STCOR-488)
      2. stripes-modules (entry points for ui modules, currently available via stripes-config getModule)
      3. stripes-web a tiny umbrella app which consumes stripes-core, stripes-config and stripes-modules

      Definition of done

      • Eliminates circular dependencies (mitigates the issues we had with reactv17)
      • Easier to update/rebuild OKAPI config file
      • Support improved stripes pre-compile bundle (goal is to make it 10X faster than now)
      • Improved cached mechanism with the use of webpack 5

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                kgambrell Khalilah Gambrell
                Reporter:
                mpk35 Michal Kuklis
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                  Dates

                  Created:
                  Updated:

                    TestRail: Runs

                      TestRail: Cases