Mike Ralphson

> [email protected] check > node --no-warnings --insecure-http-parser ./node_modules/@Mermade/api-registry/registry.js check https://developer.themoviedb.org/openapi/6453cc549c91cf004cd2a015 https://developer.themoviedb.org/openapi/6453cc549c91cf004cd2a015 FRUV expected '' to start with '/' #/paths/ ✗ Provider: themoviedb.org Fixes: 0 Saving metadata... Exiting with 1

Two API definitions, under `microsoft.com/graph` and `microsoft.com/graph-beta` should show up from tonight. Done like this to avoid clashes in version numbers (e.g. `1.0.1`).

The `info.version` field for both API definitions is `1.0.1` (unless I've done something wrong relinking the metadata) thus they would occupy the same point in our naming convention/directory-structure unless the...

Our directory structure is `./APIs/{provider}/{service?}/{version}/openapi.yaml` where `{version}` comes from the OpenAPI `info.version` field, I think it might cause more confusion if we used `v1.0` and `beta` as version numbers just...

No, that would be fine, and would allow us to put them both under a `graph` serviceName.

It will involve a small manual step to 'merge' the serviceNames baack together, so would definitely appreciate a heads-up. Will keep this issue open in the meantime. Thanks.

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

You're right @baywet, I'll reword that canned response!

Perfect, thanks for the ping!

@baywet in preparation for the above, I ran an update on your source URLs to make sure we were up-to-date. This is the output: ```shell > [email protected] update > node...