You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
As a first time seeing the code, i had difficulties understanding the relations between the components. I was thinking it would be efficient and more helpful for new contributors in the future to see a diagram explaining the structure of the app.
Describe the solution you'd like
We can integrate a UML diagram (or any other type of component diagram) in the config-server UI repo. There are multiple tools available to draw the diagram, one of them is https://app.diagrams.net/ . However if a component is added or deleted , the diagram should be modified.
Describe alternatives you've considered
The Optimal solution would be having an automated process ( for example a node module ) to generate this component diagram after each build. That way the diagram is always up to date. Until now there isn't any good solutions to make that happen so the modification should be made manually.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
As a first time seeing the code, i had difficulties understanding the relations between the components. I was thinking it would be efficient and more helpful for new contributors in the future to see a diagram explaining the structure of the app.
Describe the solution you'd like
We can integrate a UML diagram (or any other type of component diagram) in the config-server UI repo. There are multiple tools available to draw the diagram, one of them is https://app.diagrams.net/ . However if a component is added or deleted , the diagram should be modified.
Describe alternatives you've considered
The Optimal solution would be having an automated process ( for example a node module ) to generate this component diagram after each build. That way the diagram is always up to date. Until now there isn't any good solutions to make that happen so the modification should be made manually.
The text was updated successfully, but these errors were encountered: