Mike Ralphson

@Rustemsoft - It looks like your API definition did not fully validate. Please mention (@) MikeRalphson to discuss. Here is the log output:

> [email protected] check > node --no-warnings --insecure-http-parser ./node_modules/@Mermade/api-registry/registry.js check https://postman.com/collections/7445d89fda1d633e08dd https://postman.com/collections/7445d89fda1d633e08dd Fnetwork timeout at: https://www.postman.com/collections/7445d89fda1d633e08dd Saving metadata... Exiting with 1

@Rustemsoft - Closing due to inactivity - but please feel free to reopen the issue if necessary.

@cleveriot - Closing due to inactivity - but please feel free to reopen the issue if necessary.

@elianaschwartz - Closing due to inactivity - but please feel free to reopen the issue if necessary.

@bohdanl20 - Closing due to inactivity - but please feel free to reopen the issue if necessary.

Do you know if pyYAML supports YAML 1.2 or 1.1 only?

These documents are YAML 1.2, as recommended by the OpenAPI Specification: > In order to preserve the ability to round-trip between YAML and JSON formats, YAML version [1.2](https://yaml.org/spec/1.2/spec.html) is RECOMMENDED...

From https://yaml.org/spec/1.2.2/ext/changes/ > Changes in version 1.2 (revision 1.2.0) (2009-07-21) > The !!pairs, !!omap, !!set, !!timestamp and !!binary types have been dropped. `eemeli/yaml` only parses timestamp-like strings as Dates if...

It doesn't help that the YAML 1.2 spec contains three (orphan?) references to !! timestamp without explicitly referencing where it comes from.