Details
-
Type:
Task
-
Status: Closed (View Workflow)
-
Priority:
P3
-
Resolution: Won't Do
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: None
-
Labels:
-
Template:customfield_11100 15449
Description
For some time, the idea has been floating around that it might be a good idea to move all the most fundamental Stripes libraries into a monorepo. I am still not convinced by a long way, but I think it's important to give this due thought – especially, now, during the post-Madrid period where other things are up in the air (switching away from yarn link to stripes-cli, establishing testing frameworks, etc.)
Here are some useful pieces advocating monorepos – and bear in mind that they are by their nature unbalanced:
TestRail: Results
Attachments
Issue Links
- is blocked by
-
STRIPES-544 Understand all the stripes-building scenarios, and their implications for dependency management
-
- Closed
-
- relates to
-
STRIPES-543 Consider "stripes-framework" to wrap "stripes-*" dependencies
-
- Closed
-
-
STRIPES-588 Stripes 2.0 roll-out analysis
-
- Closed
-