You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now if you add an apostrophe (') to this answer, Nori parses this as {:envelope=>2013-04-12 01:00:00 +0200}. Trailing apostrophe happens often, e.g. if you mock SOAP-Answers with '...lots of ugly xml', insert some variables, find out that its best to encapsulate strings with %{...lots of ugly xml...} and just forget to remove the ' at the end. And you spend hours on debugging.
The text was updated successfully, but these errors were encountered:
Closing as won't fix. I'm not entirely convinced that this is something that Nori should fix, since the input is invalid.
Regardless, this seems to work better with modern versions of Nori. Feel free to re-open @iblue if you disagree. There's certainly room for Nori to improve its error handling, and I'd be more than happy to merge pull requests that improve any aspect of it.
Consider the following SOAP answer from our payment backend:
Now if you add an apostrophe (
'
) to this answer, Nori parses this as{:envelope=>2013-04-12 01:00:00 +0200}
. Trailing apostrophe happens often, e.g. if you mock SOAP-Answers with'...lots of ugly xml'
, insert some variables, find out that its best to encapsulate strings with%{...lots of ugly xml...}
and just forget to remove the'
at the end. And you spend hours on debugging.The text was updated successfully, but these errors were encountered: