Details
-
Type:
Story
-
Status: Closed (View Workflow)
-
Priority:
P3
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:
-
Template:customfield_11100 18944
-
Sprint:stripes force Sprint 47
-
Story Points:5
Description
TIMEBOX: 8 hours
Address the following
- When should a component no longer be in `stripes-components`
- When should a prop no longer be available on a component
- Action plan for when decision is made to deprecate.
Deliverables
- Provide recommendations/criteria for when a stripes component should be deprecated
- AND then document what should be done once a decision is made to deprecate
- Documentation should be presented at an upcoming stripes architecture meeting
- AND easily available to developers.
TestRail: Results
Attachments
Issue Links
- relates to
-
STCOM-298 Discussion: Only include presentational components in stripes-components
-
- Closed
-
-
FOLIO-1415 SPIKE: consider pre-release syntax for UI module snapshots
-
- Open
-
-
STCOM-320 Convert "dropdown" component to use 'popper' component
-
- Closed
-
-
STCOM-380 Convert "multi-selection" component to use 'popper' component
-
- Closed
-
-
STCOM-381 Convert "timepicker" component to use 'popper' component
-
- Closed
-
-
STCOM-382 Convert "datepicker" component to use 'popper' component
-
- Closed
-
(1 relates to)