Henry Andrews

@epoberezkin getting back to this now. There are several npm packages for working with stdin. From least to most complex: * https://www.npmjs.com/package/get-stdin (stdin reading with promises) * https://www.npmjs.com/package/file-or-stdin (reads file,...

@epoberezkin thanks! I'll look through all of this. I'm on-board with using get-stdin.

You've probably already thought of this :-) but ideally we can still override referenced schemas by supplying with -r, as often I'll want to test local changes without having to...

You mean it would only work by fetching over the network? That's actually against the advice of the spec: > JSON Schema implementations SHOULD implement support for current and previous...

(actually I'm not sure why I thought that quote indicated *local* support, but there are things about not overburdening schema servers)

I'll probably end up using a modified local schema for testing anyway, but wearing my json-schema-org hat, I'm still a bit concerned about an extremely popular tool regularly fetching the...

I definitely like the idea of a switch to disable standard meta schemas, whether that by default includes the meta-hyper-schema or not. In production I expect to use the standard...

@epoberezkin this is to track making the output of compile the same format as validate, correct? It turns out I'm (more or less) going to need this, because errors in...

> I probably prefer the first approach - error formatting should not be in Ajv... Makes sense. Thanks so much for the detailed guide! That will cut down on time...

OK yeah that would work. Particularly if we can use -e as a short option since in the sort of situation I'm dealing with, while it will be scripted as...