Details
-
Suggestion
-
Resolution: Duplicate
Description
Currently, the beta interface for projects implies that the relationship between projects and interfaces is one to many.
E.g. 1 Project has many Repositories, and 1 Repository can only ever belong to one project
I think it is better served as a many to many.
E.g. 1 Project has many Repositories, but 1 Repository can belong to many projects.
Here's my reasoning... I would like to visualize in some way all the dependencies that my project has. For example, lets assume that I have a package that I use across multiple projects, e.g. a CSS framework, an authentication package, a specific API interface, or even a jQuery plugin that I wrote.
With the new interface, I could theoretically visualize all the dependencies for A Project , but if I made a new project that is relatively similar, I can't visualize it in the same way, I can't add the same repositories as the current relationship is only 1 to Many.