Jeremy Whitlock

It's common convention _(or at least preference for some)_, and sometimes enforced, that sources be sorted. I would like it to be sorted alphabetically, instead of order of definition _(sub-classing...

That's a cool idea. Something like `m8 song orphans [--chains] [--instruments] [--phrases] [--tables]` _(where if you don't provide any option, you get a pretty print of all of them _(in...

What do you think about Option 2 but fields that are there purely for backward compatibility are marked as such and all API facilities are updated to work with versioning?...

The more I think about it, the more I like Option 1. It will be more effort but I think it would create the best experience.

Responses to your question: 1. I want to move away from Gulp, I don't think it's necessary anymore. 2. How so? 3. We could/should change to the oldest LTS Overall,...

I defer to your judgement. I just want to make it as easy to build/release as possible using best of breed approach in doing so. As for consumption, same thing.

The issue here is that at the root of your document, you have an invalid JSON Reference because `$ref` cannot be adjacent to any other properties. If you use `#findRefs`,...

As an API author/consumer, I am not sure that I need extra information to indicate if a response is an error or not. The `4xx` and `5xx` range of status...

Agreed, if it had to be only for the `default` value, I could hate that less. ;)

Isn't this handled [in 3.0](https://github.com/OAI/OpenAPI-Specification/blob/OpenAPI.next/versions/3.0.md#components-object) You define your reusable headers at `#/components/headers` and then use a `$ref` to reuse it. It won't allow you to have a singular reference to...