Add instructions for how to use additional violation types #58
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hellosweta
approved these changes
Jun 27, 2025
hellosweta
left a comment
hellosweta
left a comment
There was a problem hiding this comment.
Thanks for the addition to the README. 💫
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
In my project I was adding feedback for the layer violation extension but I found that danger-packwerk would ignore the violations completely when testing.
After some digging I discovered there is a violation type allowlist that needs to be provided. I think this would be helpful to list in the README so I've added a section. Let me know what you think 🙏