Open
Description
The JSON-parser doesn't seem to handle non-breaking space:
https://en.wikipedia.org/wiki/Non-breaking_space
However when examples are copied from MS Teams Chat it sometimes adds non-breaking space to JSON snippets.
We could simply replace all non-breaking spaces with regular spaces at some point (of course then it won't be possible to actually have a nbsp in a string value for instance but that need is probably small).
If the replacement is done early enough we could still support nbsp in values taken from the data source, just not hard coded in the JSON templates.
Metadata
Metadata
Assignees
Labels
No labels