Repository navigation
Make real API traces readable with expected and observed diagrams - #26
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.
Property callback logs were hard to interpret without the adapter's semantics, and the purpose of an external replay was unclear. Add a focused python-dispatch walkthrough that distinguishes assignments, new callbacks, the cumulative log and the property value, with optional expected/observed Mermaid diagrams and plain tables. A deliberately wrong expectation demonstrates the first mismatch without alleging an upstream bug.
Explain the existing rat-salsa case through its five real method calls, the adapter/runtime cost, and rendering/focus/clipboard limits. Keep ordinary native tests as the first choice and link the existing pyee #228 rather than duplicate it. Runner code, protocol and runtime dependencies are unchanged; these are current-source examples, not a new release.
Validation: 54 unit tests pass from both checkout and unpacked sdist; 3 native tests and 5 replay steps run against python-dispatch 0.2.3; wrong expectation fails at step 2; generated reports/source hashes checked; wheel/sdist pass strict metadata checks and a clean offline wheel installation. CI reruns the example and checks recorded diagrams.