Release graph-aware layout and pixel-safe SVG rendering - #23
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.
Background
Diagrams need clear typography, connectors that avoid labels and borders, and coherent overall composition. The previous millipixel SVG coordinate space also triggered browser font clamping and shape artifacts.
Implementation Approach
Testing Approach
Review Perspectives / Points of Concern
Public operations and language-intelligence contracts remain unchanged. SVG bytes/layout intentionally change. No external runtime capabilities or palette-authoring feature is added. Finite routing heuristics do not prove feasible placement for every graph; exact raster glyphs and arrowheads remain outside the geometry checker.