We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I was surprised to find that this matcher succeeds:
"JsonMatchers" should { "match type" in { val json = """{"id":1}""" json must /("id" -> "1.0") } }
IMO only selectors that are numerical types should match, so something like json must /("id" -> 1) or json must /("id" -> 1.0).
json must /("id" -> 1)
json must /("id" -> 1.0)
Interestingly, the type is taken into account the other way around:
// this fails: "JsonMatchers" should { "match type" in { val json = """{"id":"1"}""" json must /("id" -> 1) } }
Is this a known shortfall of this class?
The text was updated successfully, but these errors were encountered:
946eb1f
fix: fix #1209 use a proper type to check a string or boolean value
ad4e1d1
fix: port the fix for #1209 from main
9942bfe
and fix the non-regression for 1183
3177b69
and fix the non-regression for 1183 | Conflicts: | matcher-extra/shared/src/main/scala/org/specs2/matcher/JsonMatchers.scala
No branches or pull requests
I was surprised to find that this matcher succeeds:
IMO only selectors that are numerical types should match, so something like
json must /("id" -> 1)
orjson must /("id" -> 1.0)
.Interestingly, the type is taken into account the other way around:
Is this a known shortfall of this class?
The text was updated successfully, but these errors were encountered: