Mike Ralphson

Many thanks for the contribution. Please could you provide a link to the actual *machine-readable* API definition, in either OpenAPI or one of the other supported formats (RAML, API Blueprint,...

Many thanks for the contribution. Please could you provide a link to the actual *machine-readable* API definition, in either OpenAPI or one of the other supported formats (RAML, API Blueprint,...

Many thanks for the contribution. Please could you provide a link to the actual *machine-readable* API definition, in either OpenAPI or one of the other supported formats (RAML, API Blueprint,...

Many thanks for the contribution. Please could you provide a link to the actual *machine-readable* API definition, in either OpenAPI or one of the other supported formats (RAML, API Blueprint,...

Thanks! ReDoc blob url, e.g. blob:https://www.oembed.dev/79f8979b-b822-42cc-9169-2a22e6f1d506

Had some help from [Thomas Bayes](https://en.wikipedia.org/wiki/Thomas_Bayes). Now the `v3: true` tools with `unsure: true` are the ones that may need moving to the correct categories.

Thanks! Yes, `unsure` can be removed once a category has been properly assigned. One PR or many, I don't mind!

I've reclassified the `unsure` ones based on the full text of the project `README`s. So the guesses should now be a lot better.

I simply allowed the caller to specify a property name for it to be copied to if they wanted `$ref` preservation.

Personally, I've only ever needed to know where a `$ref` **used to be** and not what locations previously pointed into a `$ref`ed component, and although using a callback would be...