JSON serialization with forward slash '/'

Hope all is well!

Just updated to the latest release and noticed an issue with JSON serialization. The following:

map {
  'uri': "test/test"
} => json:serialize()

results in:

{ "uri": "test\/test" }

I would have expected:

{ "uri": "test/test" }

Cheers!

[apb2006]

map {
  'uri': "test/test"
} => json:serialize(map{"escape":false()})

http://docs.basex.org/wiki/JSON#json:serialize Version 8.4 Updated: unescape changed to escape.

[james-jw]

That must have changed recently? Never worked like that before nor does it any other JSON library I use including Javascript itself, any browser or .NET. I don’t use Java much so maybe that’s the catch.

For example in node or any browser this works as expected:

JSON.stringify({ uri: "test/test" })

resulting in { uri: "test/test"}

How would I produce: { “uri”: “http://test.com/test”, }

Hopefully we can go with the XQuery spec as the JSON one is wonky and there is no need for this escaping which most libraries ignore.

The only argument for doing this is easily embedding JSON in script tags, but it seems silly to enforce a rule for a process that is rarely done. I don’t think I have ever embedded JSON in a script tag. 😃

it would be great if there was a way to decide which to use, like an option.

Cheers either way!