Lorna Jane Mitchell

I am tentatively in favour of looking at adding the docs-output-filename as a per-API configuration and supporting multiple APIs for docs the same way we do for lint and other...

Let's do #1250 first, since it reduces the complexity on this task.

I think adding `docs-output` as a config file option is a good way forward. How about `docs-output` to match the `build-docs` command? This should be supported in the config file...

Maybe it makes sense to also name it `--separator` here? It would need different help text though in the context of this command. Something like "Object key separator used when...

Where is it used? Could we use `--key-name-separator` or does that make it more confusing?

Related (but not actually fixing the problem): a good description of the rules that AWS gateway expects: https://github.com/stoplightio/spectral/issues/475

This is a nice idea! I think it would be great to have descriptions of rules, and to be able to get a ruleset in summary-for-humans format. I especially like...

Looping back on how this should look. I think we should use an OpenAPI -style description for our rules. So 1-2 sentences of markdown is the expected format, but not...

I had wondered if that was a common use case, I guess we don't have glob on aliases or ways to group which aliases should be linted. I can see...

To recap, these are the use cases I think we need to support: - Lint files by filename - Lint files by glob to match path to file - Lint...