feat: inspect port and edge values - #74
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.
Description
This PR adds type-aware port tooltips and click-to-inspect support for handles and edges. A handle descriptor can now include a
type, which renders with its label on hover. Handle and edge clicks emit events with their IDs and screen position, andReactFlow.show_popup()renders a dismissible Panel overlay for application-specific value inspection.The popup child is included in ReactFlow's child-model synchronization, and event callbacks are dispatched in the triggering document pass so callbacks can safely update child viewables.
Minimal example:
How I tested:
pixi run -e py312 testpixi run -e test-ui test-ui(48 passed,2 reruns)pre-commit runon all changed filesAI Disclosure
Tool & Model: Kilo Code,
kilo/openai/gpt-5.6-terraUsage: I used it to implement the feature, investigate the child-view synchronization issue found during browser testing, write tests and documentation, and run validation.
Checklist