[graph/canvas] refactor: implemented theme-driven cursor system#660
Merged
Conversation
teykamp
reviewed
Jun 11, 2026
teykamp
requested changes
Jun 11, 2026
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
2 participants
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.
Replaces the imperative GraphCursor plugin (with disabled, graphToCursorMap, activateCursorSelectMode) with a theme-based cursor system. Cursor state is now derived from the theme stack on each draw rather than managed through ref mutations scattered across plugins.
canvas.cursor theme key controls the global cursor; CURSOR_FALLBACK defers to element-level keys (eg. node.default.cursor, marquee.encapsulatedNodeBox.cursor)
Each plugin/feature that needs cursor control owns a small useFooCursorTheme composable that sets/removes its theme entries on activate/deactivate
Renames GraphUnderCursor.items → .elements and moves drag state to shared/drag/