Repository navigation
Keep graphs readable in mobile and narrow reports - #13
Merged
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The mobile graph stacked every node in one column, so evidence links looped around intervening cards and the diagram became too tall. Graph layout now responds to its own width. Related inputs share a row on narrow reports, and connections enter the next stage through separate top ports. Links that skip stages route around nodes instead of crossing them.
The shared renderer keeps website and skill reports consistent. Prepares version 0.2.5.
Validation: 70 tests pass, including routing checks for fan-in, skipped nodes, and both desktop directions. Lint, types, build, site/package and inline smoke checks pass. Browser checks at 320, 390, 768, and desktop widths, a 400px pane inside a wide window, and an eight-node fixture show no page overflow, clipped paths, or paths through nodes. Node selection still shows the matching evidence; browser logs are clean.