Fix bug where deep matcher expects a map passed into the matches function#3
Merged
fibulwinter merged 1 commit intodart-lang:masterfrom Mar 6, 2015
Merged
Conversation
fibulwinter
added a commit
that referenced
this pull request
Mar 6, 2015
Fix bug where deep matcher expects a map passed into the matches function
Contributor
|
Thanks, Ted |
mosuem
pushed a commit
to dart-lang/test
that referenced
this pull request
Oct 17, 2024
Fix bug where deep matcher expects a map passed into the matches function
davidmorgan
pushed a commit
to dart-lang/build
that referenced
this pull request
Mar 23, 2026
Fix bug where deep matcher expects a map passed into the matches function
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.
Get around a bug in core matchers where matchers expect a non-null map value for deep matcher. See: dart-lang/test#2320