-
From [JSON standard](http://www.ecma-international.org/publications/files/ECMA-ST/ECMA-404.pdf):
> Insignificant whitespace is allowed before or after any token. The whitespace characters are: charac…
-
I got `Error executing query: server error (parsererror)` when trying to find traces. This happens after update from Zipkin 1.7.0 to 1.8.2 today. Spans that I send are somehow problematic for the newe…
-
Link: https://github.com/wordnik/swagger-spec/blob/master/versions/1.2.md
- Section 3: a "fully qualified URL" can be defined as a "URI, as defined by [RFC 3986, section 3]; the scheme used by this U…
-
We've been seeing a lot of strange errors in logstash logs complaining about normal errors but dumping the event in what appears to be this weird nested format. Here's an example..
```
{:timestamp=>…
-
Hello kgabis,
As per json.org, null is a valid JSON value.
I would expect the following code to print "parsing null success!". Instead it prints "cannot json_parse_string null".
``` c
#include
#i…
-
This code:
``` cpp
json j = { { "foo", 65536 } };
int16_t v = j["foo"].get();
std::cout
-
I am trying to parse this json:
"window": {
"texture": "interface\\ifcommon\\slibifwnd.ddj",
"width":330,
"height":366,
"position": [0, 0],
"rect": [0, 0, 330, 366],
"moveabl…
-
The JSON API spec references [RFC 4627](http://tools.ietf.org/html/rfc4627), which has been obsoleted by [RFC 7159](http://tools.ietf.org/html/rfc7159).
-
RFC 7159 is consistent in its use of "member" and "members", let's follow suit. As a bonus, we can eliminate awkward references to our "properties" property.
-
If I'm understanding the JSON standards correctly, tabs are not allowed. I'm posting a json to my api (the whitespace at the end of the value is a tab character). This is what's happening in the bac…