-
-
Notifications
You must be signed in to change notification settings - Fork 71
Open
Labels
enhancementNew feature or requestNew feature or request
Description
Hi!
If I understand correctly current behavior of Ignoring Violations, an explicit path to a component needs to be given.
It's later compared literally, in the code, if I read code correctly:
vacuum/utils/filter_ignored.go
Lines 16 to 19 in 27c9ce4
| for _, i := range ignored[r.Rule.Id] { | |
| // Check if the single Path matches | |
| if r.Path == i { | |
| found = true |
In my project I have quite a lot of ignore rules to set.
Can this behavior be upgraded, so a valid JSON Path can be given as ignore rule and then evaluated in the code as such?
That would be useful especially because of the wildcard selector [*] (https://www.rfc-editor.org/rfc/rfc9535.html#name-wildcard-selector)
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or request