-
**Describe the issue**
We have a requirement where we need to display the Locks owned by a user in a particular workspace.
In our development scenarios we have multiple workspaces where same repo w…
-
**What is the bug?**
Sending a predict request to a model that uses SageMaker connector like so
```
POST /_plugins/_ml/models/_6gdD40BZqSAbrEiV6DT/_predict
{
"parameters": {
"inputs": "tes…
-
The literal representation of certain negative numbers is not being properly preserved.
Consider:
```
./jq --version
jq-1.6-268-gc99981c-dirty
./jq -nM '1E1000'
1E+1000
./jq -nM '-1E1000…
-
Example:
```cpp
// In ANSI (GBK) encoding
auto e = glz::validate_json(R"({"key":"value中文"})");
// In UTF-8
auto e = glz::validate_json((const char*)u8R"({"key":"value中文"})");
```
![image](htt…
-
### Current behavior
When converting a yaml content with float props values, the json output value uses the wrong decimal separator
![image](https://github.com/veler/DevToys/assets/16958254/463b667…
-
Unicode code points in the range U+D800 to U+DFFF are used for encoding UTF-16 surrogate pairs, and can not occur on their own in a valid Unicode sequence. However, the `\uHHHH` escape sequence can be…
GULPF updated
2 years ago
-
OAS 3.0 and 3.1 explicitly define `"integer"` as an allowed value of the `type` keyword in section [Data Types](https://spec.openapis.org/oas/v3.1.0.html#data-types).
This difference between OAS an…
-
## Description:
I encountered an issue when parsing a JSON object into a sealed trait. It fails depending on the order of the fields. Parser expects `type` field to be the first one.
According to…
-
### Describe the bug
Is this JSON formatting performed by `to json` intentional?
```
{
"version": "v0.4.4",
"notes": "blablabla",
"pub_date": "2024-05-04T16:05:00Z",
"platforms":
{…
-
# Current state & Rationale
Yojson currently supports JSON parsing as defined in RFC 8259 with a couple of extensions: variants, tuples and comments (the latter not documented).
JSON is a format…