GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This is related to: #1442
auto json = Json();
Json should allways serialize to a valid Json I think. So probably to null in this case?
undefined is not valid JSON, tbh, I'm not sure why vibe.d even included it seeing as Json.emptyObject["foobar"] != Json.undefined
Json.emptyObject["foobar"] != Json.undefined
Json.undefined may be returned when referencing a key that is not present in a Json object. It should not be serialized to anything, except when at the root of the tree, then it should be serialized as null.
@thaven except Json.undefined != Json.undefined
Json.undefined != Json.undefined
@dcousens One may argue if two non-existing 'things' should be considered equal... ;-) That is probably why the type of the Json object is being compared to Json.Type.undefined.
@thaven in JS, undefined === undefined, fwiw
undefined === undefined