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
{{ message }}
This repository has been archived by the owner on May 21, 2018. It is now read-only.
Some further testing was done, and this issue was definitely jawn related. Looks like it works on Json4s and Argonaut, but seems to fail for the others. Jackson actually gives a useful exception which says that the control character 11 needs to be escaped with a backslash. Jackson is right, according to RFC7159 (https://tools.ietf.org/html/rfc7159#page-8), this should be escaped.
Rapture should take a conservative stance on what is allowed inside an interpolated string. So making that a compile error would be better.
The text was updated successfully, but these errors were encountered:
Yeah, that's definitely a Rapture issue with the substitution. If I recall correctly, it serializes res33 to a String then substitutes it into the expression. This means that the serialization is wrong.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I hit an issue in a production system with this string using the jawn backend:
Some further testing was done, and this issue was definitely jawn related. Looks like it works on Json4s and Argonaut, but seems to fail for the others. Jackson actually gives a useful exception which says that the control character 11 needs to be escaped with a backslash. Jackson is right, according to RFC7159 (https://tools.ietf.org/html/rfc7159#page-8), this should be escaped.
Rapture should take a conservative stance on what is allowed inside an interpolated string. So making that a compile error would be better.
The text was updated successfully, but these errors were encountered: