Create design_registry table to track design repositories
Problem to solve
In order to replicate design repositories, we need to store design repository data in a separate table to avoid race conditions and to make the code easier to understand.
Further details
Proposal
-
Create design_registry
as a separate table -
Extract project/wiki registry code where ever it makes immediate sense or accepts some duplication of code in the first iteration.
Documentation
I don't believe new documentation is required for this.
Testing
TBD