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
I noticed that scanners and hooks use a different approach in their directory structure.
For the scanners there are subdirectories for parser and scanner (if existing) while the source code for the hook resides directly in its root directory.
I think we should introduce a hook directory inside each hook containing its source code to make their structure more clean.
Activity
[-]Align Hook Directory Struckture With Scanner[/-][+]Align Hook Directory Structure With Scanner[/+]rfelber commentedon Jun 16, 2021
Hi @fuhrmeistery,
thx for this issue, i totally agree with you :-)
I had the same idea and problem which came up implementing my documentation PR #475
Update Makefile For finding-post-processing
Update Makefile For finding-post-processing
Add `hook` Directory To Cascading Scans
Add `hook` Directory To Cascading Scans
Add `hook` Directory To persistence-defect-dojo
Add `hook` Directory To Persistence Elastic
Add `hook` Directory To Teams Webhook
Add `hook` Directory To Update Field
28 remaining items
Add `hook` Directory To Cascading Scans
Add `hook` Directory To persistence-defect-dojo
Add `hook` Directory To Persistence Elastic
Add `hook` Directory To Teams Webhook
Add `hook` Directory To Update Field
Change Directory For Building Hook Images
Change Directory For Notification Hook
Add `hook` Directory To Cascading Scans
Add `hook` Directory To persistence-defect-dojo
Add `hook` Directory To Persistence Elastic
Add `hook` Directory To Teams Webhook
Add `hook` Directory To Update Field
Change Directory For Notification Hook
Add `hook` Directory To Cascading Scans