Closed nkbt closed 8 years ago
\b
is ok for some reason. But other combinations like \a
, \c
fail too.
This is almost certainly a problem with upstream - there's nothing in this module that should affect string escaping
Thanks. Will move it there then On Wed, 8 Jun 2016 at 16:41, Glen Mailer notifications@github.com wrote:
This is almost certainly a problem with upstream - there's nothing in this module that should affect string escaping
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/glenjamin/transit-immutable-js/issues/20#issuecomment-224501589, or mute the thread https://github.com/notifications/unsubscribe/AAKsoGXUp7jNkukKzQ3iyAweGswEOlurks5qJmI-gaJpZM4IwkpD .
Closing for now, will reopen if not upstream issue.
It could be purely
transit-js
issue, will move to upstream if not the problem oftransit-immutable-js
My JSON after encoding looks like this:
Some context: this is universal JS app, I serialize Redux store on a server (partially immutable-js, partially plain objects) and then I am trying to deserialize it in a browser. Accidentally my route had
something\something
in it, and that\s
brokefromJSON()
because backslash was not escaped.Expected value: