Repository navigation
feat: add DependencyGraph and configurable graph controls - #46
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.
Adds DependencyGraph for skill trees, technology trees and synthesis recipes. Nodes are laid out automatically, dependency paths can be highlighted, and custom renderers can own the complete node surface for image nodes or Flip cards. Node/edge anchors use normalized coordinates, with edge-specific overrides.
NodeGraph and DependencyGraph now allow individual viewport buttons to be hidden, custom actions to be appended and the toolbar to be positioned. Initial fitting completes before visible-node culling is enabled. The package exports and optional stylesheet include the new component.
Validation
Tested commit:
c05502dc749550162842e32edff86b7a372b5162; base:fbe25a47085c77e088781328eb17019d24b7204c. The worktree was clean during validation.npm run check:repositorypassed.npm run buildpassed; this result is reused for unchanged shipped sources after the package-boundary test-only follow-up.node --test packages/inkra/test/node-graph.test.mjs packages/inkra/test/package-boundaries.test.mjs: 7 passed, 0 failed, 0 skipped, using Node 24.19.0 / React 19.3.1 on macOS arm64 at the exact committed head.Required package/installed-consumer checks and all other selected component tests remain enabled. This PR does not publish npm; the documentation deployment will pin the merged source candidate.