Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
JSON matcher *any-object* is misinterpreted
See original GitHub issueHi there, thanks for your work!
I am using JSON matchers extensively in my application and I realised that in 2 HTTP responses with exactly the same JSON object (within another object), in a test I can match it with *any-object*, but in another test, I have to fully describe it.
In both tests i am using “Then assert body.is(…)”
The failing test tells me:
“matcher any-string (checks if the field is a String) failed for input (…)”
I have tried to match with object, so why the test fails to match with string ?
This wouldn’t be so weird if it never worked, but as i said, i works in another test, that tests exactly the same object. Any help would be very much appreciated
Issue Analytics
- State:
- Created a year ago
- Comments:19 (11 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Actually, we have a fork of play 2.5 and that wouldn’t work for us. I have to push the Core team to get up to date with that, and also with the version of your lib, cause we use currently the 0.19.3, but I want all the recent goodies 😃
Thanks, I think I have an idea 👍