Repository navigation
docs: record nested binder client probe - #597
Merged
Merged
Conversation
2 tasks
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.
Summary
Record the nested-binder probe pair on client
2.25.0.1 - 154504.1(zh-CN). The lambda rule appeared but produced the client's nesting error; the source-position control appeared without an observed error. The result establishes a boundary for the tested shapes, not every binder combination.The capture includes fixture and localized input hashes, the original client message, and the localization method. wrightkit/wright#1046 tracks the decision on lint classification.
Refs #521
Verification
git diff --checkThe client test did not measure runtime behavior.