-
Notifications
You must be signed in to change notification settings - Fork 0
Where to Maintain This Repo
Wesley B edited this page Feb 20, 2024
·
5 revisions
This repo has been maintained at TACC/Core-Styles and TACC/tup-ui:/libs/core-styles. Neither syncing the two nor using one or the other has been ideal.
A. Maintain Only TACC/Core-Styles
✅ Obvious and intuitive usage or a library that has multiple clients.
- Library can be familiarly installed from NPM at reliable releases.
- Library can be easily installed at stages of development e.g. branch, commit, latest, pre-release, tag.
- But this challenge exists for TACC/Core-Styles and TACC/Core-CMS and TACC/Core-Styles and TACC/Core-Portal.
- See TACC/Core-Styles: Develop with Client Code Simultaneously.
- Version v1.0.0 (in development, as of 2022-11) will allow more reliable testing before installing on client.
B. Maintain Only TACC/tup-ui:/libs/core-styles
- But this challenge exists for TACC/Core-Styles and TACC/Core-CMS and TACC/Core-Styles and TACC/Core-Portal.
- Version v1.0.0 (in development, as of 2022-11) will allow more reliable testing before installing on client.
- See TACC/Core-Styles: Develop with Client Code Simultaneously.
- obtuse command (arcane repair)
- git submodules (team dislike)
- third-party service (unreliable maintenance)
C. Maintain Both TACC/Core-Styles And TACC/tup-ui:/libs/core-styles
❌ Syncing architecture changes is common and difficult.
- Architecture changes are common because Core-Styles is still a Work in Progress (v0.11.0).
❌ Syncing pattern updates in both directions is tedious and cumbersome.
- TACC/tup-ui and TACC/Core-Styles may add or edit the same pattern.
- Tracking which patterns to sync in which direction is not worth the overhead.
❌ Maintaining two instances of one library should not be necessary.
- It seems like a failure of architecture, not a solution.