René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":":construction:  [Consistency] Ensuring file/code consistency for scanners","articleBody":"As a secureCodeBox developer and maintainer I would like to have consistency between all provided resources, especially scanners. This should speed up the development process, enable a consistent documentation and make maintenance simpler.\r\n\r\nConsistency can be achieved manually by aligning all existing files manually, I think the best and most sustainable way would be to have tests (in the ci pipeline), that point out on inconsistent file and coding standards.\r\n\r\nFiles that should be considered for scanners:\r\n- [x] **Chart.yaml** (#685)\r\n- [x] **values.yaml** (#693)\r\n- [x] templates/**cascading-rules.yaml** (#691)\r\n- [x] templates/scanner-name-**parse-definition.yaml**\r\n- [x] templates/scanner-name-**scan-type.yaml** (#689)\r\n- [x] *parser*: All parsers should be tested for an empty / erroring result file (#701)\r\n- [x] *parser*: All parsers should have the same output standard for findings (see #619)\r\n\r\nEnsuring consistency in the future:\r\n- [x] Create template files and a make command to automatically create a new scanner directory with consistent files (#684)\r\n- [x] Change documentation where necessary ","author":{"url":"https://github.com/SebieF","@type":"Person","name":"SebieF"},"datePublished":"2021-08-31T14:41:52.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/620/secureCodeBox/issues/620"}