Juan Cruz Viotti
Juan Cruz Viotti
:+1: On JSON-e. I think we should avoid defining stringified complex computational syntax.
> @jviotti And yet we support Regex 😉 @mwadams True, but then regexes are somewhat standardised. My point was to indeed take something like JSON-e instead of defining our own...
I like the proposal. I wonder if we need another category for keywords (like assertions, applicators, etc) that goes something like "modifiers", so we have a word to talk about...
For example, in my case, just to get the ball rolling: - I'm investing a ton on time trying to educate people on JSON Schema. Including learnjsonschema.com and the premium...
@Julian You are also doing some maintenance on the test suite too as far as I could see, right?
I like the idea, but my main concern is that if most of these formats are optional, very few will actually implement them, rendering them mostly unusable for any interoperable...
I vote for "smaller issues up front, then the big edit" for the following reasons: - There might be a lot of little ones that are easy and we can...
Given the current change of options, Option 4 sounds good.
Makes sense. Let's discuss @kwennB. Some of these things are easy to add to learnjsonschema.com (or are already there), but some I'm not sure. For example: > - Creating a...
The diff is huge, as all the schemas are getting formatted, but no semantics are changed. Just indentation and keyword ordering. At least they seem much nicer to the eye...