Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is just a strawman proposal - feel free to close if you like it less than the current pattern.
I was experimenting with a custom rule in my codebase and was able to set it up with a relative path in the JSON config without a problem. Seeing the examples here, I was curious why they need to use absolute path, but AFAICT, it seems to be because of using
go build
on a single file rather than module. I restructured so the module can be built more simply - becauserules
has ago.mod
it doesn't change the fact that rules are not in the instrumented app. Does this seem like a worthwhile cleanup?