Is the use of $ref compliant with OpenAPI 3.0.3 specification?

[davidmoten]

I don't see mention of support in the OpenAPI specification 3.0.3 or 3.1.0 for using $ref at the levels shown below in this top level index.yml:

openapi-specification/specification/index.yml

Lines 22 to 28 in 2e52e97

	paths:
	$ref: "./paths/_index.yml"
	components:
	parameters:
	$ref: "./parameters/_index.yml"
	schemas:
	$ref: "./schemas/_index.yml"

The reason I raise this is that I don't see these fields available in the results from parsing your specification with the java artifact io.swagger.parser.v3:swagger-parser:2.1.13 and after checking the specification I'm supposing your yaml specification is not compliant with the standard. Is that the case?

[wangela]

If you would like to upvote the priority of this issue, please comment below or react with 👍 so we can see what is popular when we triage.

@davidmoten Thank you for opening this issue. 🙏
Please check out these other resources that might help you get to a resolution in the meantime:

• Check the issue tracker - bugs and feature requests for Google Maps Platform APIs and SDKs
• Open a support case - Get 1:1 support in Cloud Console.
• Discord - chat with other developers
• StackOverflow - use the google-maps tag

This is an automated message, feel free to ignore.

[amuramoto]

Correct - there are currently quite a few misuses of $ref in the spec in this repo. I've been working on ferreting them out, but it will take some time since it's being done as part of a larger overhaul of this repo. I'll leave this issue open until that is resolved