You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: