Repository navigation
feat(architecture): draw --forbid violations red - #49
Merged
Merged
Conversation
A violating file edge is drawn red and thicker. Under --group-depth the directory edge it rolls up into is marked. --max-render is not overridden to force a violation into the picture; a stderr note counts the hidden ones, and the run still exits 1. Without violations the DOT is byte-identical to a run without --forbid.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Roadmap item 2: the diagram now shows where a
--forbidrule breaks, not just stderr.color="#dc2626", fontcolor="#dc2626", penwidth=1.8: the one loud color in the muted house style.--group-depth:violatingDrawnKeysmarks the directory edge a per-file violation rolls up into. A violation that rolls into a single group isn't drawn.--max-renderis not overridden to force a violating edge into the picture.hiddenViolationNoteprints how many were left out; the run still exits 1.--forbid(tested).--checkignores color, so committed diagrams are unaffected.Real render: codegraph's own repo, full scan (4.0s),
--group-depth 2 --max-render 12 --forbid 'src/mcp/->src/db/': exit 1, 3 violations listed,src/mcp/ → src/db/drawn red.Local:
node test/run.js195 passed, 0 failed (fork codegraph). Docs: README, USAGE, TECHNICAL.md.