Remove stripes web parts from stripes-core
Description
Environment
None
Potential Workaround
None
clones
is blocked by
relates to
Checklist
hideTestRail: Results
Activity
Show:
Michal Kuklis April 10, 2023 at 8:53 PM
We decided not to pursue this given we found a workaround in order to move the transpilation forward.
This work can be still valuable in the context of the webpack federation.
Khalilah Gambrell January 30, 2023 at 4:18 PM
@Michal Kuklis - based on conversation with stripes-force team, moving this to Poppy.
Won't Do
Details
Details
Assignee
Michal Kuklis
Michal KuklisReporter
Michal Kuklis
Michal KuklisLabels
Priority
P3Sprint
None
Development Team
Stripes Force
Release
Poppy (R2 2023)
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created November 28, 2022 at 8:47 PM
Updated April 10, 2023 at 8:53 PM
Resolved April 10, 2023 at 8:53 PM
TestRail: Cases
TestRail: Runs
This work is mostly described by:
https://folio-org.atlassian.net/browse/UXPROD-2889
We need to remove the parts which are not exposed by:
https://github.com/folio-org/stripes-core/blob/master/index.js
into a separate project (stripes-web or stripes-ui).
The parts exposed currently by stripes-core should stay as it is.
All references to dynamic stripes-config should be moved to stripes-ui