I’m looking at the API and am seeing that ‘/’ is escaped to ‘\/’ in its output. Is that a feature or a bug?
Could well be a feature. If yes, is that the only character that’s escaped? I haven’t found an example of a more complex URL (with ‘&’,’?’ and other reserved characters).
It does look like the API is emitting something similar to JSON-LD. But then the '/'s shouldn’t be escaped?
I’m keeping this email brief. Could be a can of worms. Or response could be, “That’s how we do it.”. I’ll deal with the latter if that’s the case.