| | | Breaking change? - mark with X | Prioritization - Zak ($100) | Prioritization - John ($100) | |
|---|
Maintain (Infrastructure) | | Encourage teams to implement - STRIPES-904: [SPIKE] Explore creating a unified GitHub Actions workflowClosed Next step: (Action item John creates Jira issues) for PR stripes-core Noah has sample PR1393
PR stripes-component PR ui-development
Then create issues for other ui-repos after John and Zak validate
Spike - define technical approach Outline options (Action item: Zak) - Estimated time (2 days) Review options with John and send a note to stripes-update/stripes-architecture for awareness and additional participation (Get all feedback timeframe: 2 weeks) KG can create stories for Spitfire/Corsair to provide feedback. DevOps review > need TC support?
| | $40 v4.1 seems to Just Work for repos, for platforms, for workspaces. YAY! it’s our cruftiest cruft. fix the worst first. blocks other dependency updates (favicons, maybe others) It’s easy and we could use the quick win. Can be rolled out incrementally across repos/teams Must be done in each repository but does not need to be coordinated.
| $20 | |
Maintain | upgrade react-router from v5 to v6 - I suspect the impact will be very small or very large, as in, some repos won't be affected at all but others will have to do some heavy lifting. This work will have to be done all at once.
| react-router POC or analysis to determine estimate Impacts all ui-repositories. All must repos must upgrade. BREAKING CHANGE sidecar environment? no-need for a rancher environment / use a ui-build Communicate!!!!
| X | $0 Next time, I’m putting most of my cash in this basket since and sprinkling the rest among the other “update old things”. Must be done in each repository AND coordinated across them, so even if the work is easy the effort is large.
| $5 | |
Innovation | | | | $20 gotta follow ecosystem SOP enables MARVA (or any third party) to consume us must be done in each repo but can be done separately
| $20 | |
Improved dependency handling support | commit yarn.lock in all modules enable dependabot in all modules
| To consider this feature > Verify with Noah’s work and/or with DevOps | | $30 | $10 | |
Improved developer adoption | | | | | | |
Accessibility | | In Progress Next steps: John to revise goals/objectives cell. | | | | |
Accessibility | | | | | | |
Break tower of knowledge/support | | | | | | |
Bolster UX consistency | | | | | | |
Improved test coverage | | | | | | |
| DayJS - Switch ui date-time library from using the EOL’d moment library. In Progress | In Progress | | | $8 | |
Maintain | Popper -> convert to Floating UI | Dependency update Possible delegate candidate | X | | $3 | |
Maintain | Downshift -> Update to most recent version (lots of breaking versions since) | Dependency update Possible delegate candidate | X | | $3 | |
Maintain | react-highlight-words | Dependency update Possible delegate candidate | | | | |
Migration | redux-form and react-form and their related libraries have been abandoned. We already contend with some peer-dep warnings for related libraries that haven't provided a React v18 release (which means they've been out of date since at least March, 2022). The main contenders for replacement are formik and react-hook-form. We don't need a "thou shalt switch" decree, but we should do a spike to see how stripes-components interacts, pick our favorite, and write a guide. I would vote for RHF first. This work can be done incrementally. | Select a new form library selection | | $10 don’t change the old stuff, but provide a clear path for new stuff stops us from accumulating debt can be done in isolation in stripes-components
| $10 | |
Maintain | react-query: we're on v3; current is v5. Dunno the impact. This work may be doable incrementally but all at once is preferable. | | | | $10 | |
| | | | | | |
| | | | | | |