-
JSON produced by `ConstraintSet$WriteJsonEngine` from method `ConstraintSet#writeState(0)` does not follows RFC 8259 or 4627 standards.
For example in WriteJsonEngine as key punctuators used single…
-
I'm confused about the precise nature of the relationship between `ejs` and JSON. Specifically, the package description for `ejs` says this:
> A no-compromises implementation of RFC 8259 in which a…
-
### What type of request is this?
New tool idea
### Clear and concise description of the feature you are proposing
Convert between unicode symbols (💯) and JSON escape sequences (\uD83D\uDCAF).
###…
-
BPO | [40090](https://bugs.python.org/issue40090)
--- | :---
Nosy | @rhettinger, @terryjreedy, @ezio-melotti, @amaajemyfren
PRs | python/cpython#19197
*Note: these values reflect the state of the iss…
-
RFC 8259 says that extended plane characters may be encoded as a UTF-16 surrogate pair using the "\uXXXX" sequence. For example, it says that U+1D11E may be represented as "\uD834\uDD1e". Json.unescap…
-
#### Repro steps
Provide the steps required to reproduce the problem:
1. Create a powershell function with the following parameters
![image](https://user-images.githubusercontent.com/16194643/1…
-
This issue was inspired by the discussions on issues #1766 and #1870. It replaces those two issues, so I will close them once I create this issue.
### The Problem
Once upon a time, the `metadata…
-
**Is your feature request related to a problem? Please describe.**
The engine currently violates the JSON spec by not normalizing Unicode escapes. We do this for performance purposes, since ordinal c…
-
When using `klv` and `serialize` arrows to serialize klv metadata to json,
sometimes I get invalid JSON that can not be parsed properly
due to the following key value pair: …
-
It would be convenient if unit names containing backslashes (like "\##/") escaped the backslashes in json. I wish for
"name": "\\\\##/ (2918)"
instead of the present encoding, which …