Mike Ralphson

Neither OpenAPI 2.0 or 3.0 supports `type` taking an array. I believe this is an error of omission in the 2.0 spec, but it is [called out explicitly](https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.0.md#schema-object) for 3.0...

What is your expected (non infinite) output if all internal references are to be replaced?

That is exactly the output if you **don't** specifiy `resolveInternal: true`.

This is unrelated to `oas-resolver`. This is purely due to Speccy's `yaml` parsing and serialization functions. `4:23` cannot be interpreted as a boolean, number or null, therefore it is a...

2019-10-10 cannot be interpreted as a boolean, number or null, therefore it is a string by default and does not require any quoting. Probably a bug in SwaggerHub.

From the OpenAPI spec: > In order to preserve the ability to round-trip between YAML and JSON formats, YAML version 1.2 is RECOMMENDED along with some additional constraints: > Tags...

I said it was probably a bug in SwaggerHub. If they're not limiting their yaml parsing to the JSON Schema ruleset, then that's a bug.

All issues here should be closed. Speccy is unmaintained.

Ah, apologies for misreading.

Not so far. If you have an immediate requirement, you could try https://apimatic.io/transformer