Greg Dennis
Greg Dennis
Hm... it seems their playground (and thus their implementation) doesn't match up with what their spec says. This actually generates an error (in my code): > The ! rule needs...
Oh, the JS implementation is reading an array with multiple values and then interpreting that as the value. I think I grasped that in my first comment, then forgot it....
But then, truthiness for an array means that it's non-empty, and the result of `[{ "var": "a" }, false]` with an empty object as data is `[null, false]`, which is...
> In json-logic-js and json-logic-php, > > { "!": 1 } > > is supposed to be the same as > > { "!": [1] } In that specific example,...
I really don't have a preference of how this gets fixed, honestly.
> LLMs (such as GPT-4o) use the order of the properties as defined in the schema for structured outputs (see [OpenAI docs](https://platform.openai.com/docs/guides/structured-outputs#key-ordering)). LLM generation uses previously generated tokens in its...
I do have [tests](https://github.com/json-everything/json-everything/blob/master/src/JsonSchema.Generation.Tests/PropertyOrderTests.cs) for property ordering in schema generation. I would expect this to be honored by the loop in the serialization converter. Can you provide an example where...
This should be resolved with v8. The initial JSON representation is preserved via `JsonElement`.
Yeah, I saw this, too. I'm not really sure what it is. Everything still seems to work just fine as far as I can see.
the error should be fixed now. Thanks for the report.