364 add dependency graph to GitHub and gitlab tickets using mermaidjs#427
Conversation
… improvements still
| } | ||
|
|
||
| // this function returns a string containing a mermaids js flow chart to the given pURL | ||
| func (g *gitlabIntegration) renderPathToComponent(assetID uuid.UUID, assetVersionName string, scannerID string, pURL string) (string, error) { |
There was a problem hiding this comment.
I think you can reduce the duplication of this logic by creating its own function, which gets the component repository as parameter. And please write a test for it 🙂
|
Code is ready .The only thing left to do is write tests |
removed the debug bin file Signed-off-by: Patrick <patrick.rissmann@l3montree.com>
|
Disclaimer I know that the FormatNode function should not be public but i can't use it in the integrations_text package otherwise. |
Maybe it is just simpler to change the mermaidjs diagram from |
…orientation of the flowchart
Merging this branch changes the coverage (1 decrease, 1 increase)
Coverage by fileChanged files (no unit tests)
Please note that the "Total", "Covered", and "Missed" counts above refer to code statements instead of lines of code. The value in brackets refers to the test coverage of that file in the old version of the code. Changed unit test files
|
Issues now show a mermaid flow chart with the individual components in their description . Could need some artistic and formating improvements.