This fixes #1953 by adding a list of UUID false positives. It also renames the lists so they appear together in the file explorer (nitpick).
For things like UUIDs it doesn't make sense to use the standard IsKnownFalsePositivr function because the pattern is so specific. Perhaps it's worth adding a UUID-specific one to catch stuff like 00000-0000-...?
It also changes a few things:
Remove the detectors label so false positive unit tests can catch issues more frequently
Changes the DefaultFalsePositives from a slice to a map to allow for exact matching
Checklist:
[x] Tests passing (make test-community)?
[x] Lint passing (make lint this requires golangci-lint)?
Description:
This fixes #1953 by adding a list of UUID false positives. It also renames the lists so they appear together in the file explorer (nitpick).
It also changes a few things:
detectors
label so false positive unit tests can catch issues more frequentlyDefaultFalsePositives
from a slice to a map to allow for exact matchingChecklist:
make test-community
)?make lint
this requires golangci-lint)?