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.
Why does JsonMatcher accept an invalid JSON string?
See original GitHub issueIt appears that the JsonMatcher constructor accepts an invalid JSON string, and swallows the parsing exception.
Is there a valid use case for this behavior? As far as I can tell, it still won’t properly match an invalid JSON string. For me, the preferred behavior would be to let the caller know right away that the string is not valid JSON.
I would be happy to submit a pull request with this change, but I wanted to make sure I’m not missing something.
Thank you much, this is a fantastic tool that we use every day!
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (2 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
Parsing the code in the constructor : you can try this in preview MyGet :
WireMock.Net.1.2.17-ci-13680.nupkgI also think that throwing exception in constructor is correct. You get this exception immediately when adding a invalid mapping.
Later today I will merge PR and create new official release.