Skip to content

Violations vs References #8

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
baweaver opened this issue Apr 11, 2025 · 1 comment
Open

Violations vs References #8

baweaver opened this issue Apr 11, 2025 · 1 comment

Comments

@baweaver
Copy link

One issue that was brought up when I was trying to rewrite parts of this tool elsewhere was that it only highlights violations, meaning any package overrides declaring something a dependency or an exception will cause that reference to not be highlighted.

Eventually this tool should transition to using all references from Packwerk and distinguishing between current violations and "allowed" violations so we can get a fuller picture of the codebase.

That all said, would be willing to chip in on that note and design a solution later.

@martinemde
Copy link
Collaborator

I definitely agree that this would be useful. I've been shortcutting lately by removing dependencies on the packs I'm looking at. In the long run, being able to show that code without hacking the package.yml would be a better solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants