We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Related to #83, #84
After the PR was merged, it was rolled back in this commit: 540b249#diff-38bb6d02d3442ac95d8613ef4fed0b1cb70f7bc2001d1abe71bafbede04a0dd1
- SchemaOrReference items = 30; + ItemsItem items = 30;
As the comments in the latest code say, I also agree that the wrong model is being used.
gnostic/surface/model_openapiv3.go
Lines 386 to 397 in ad271d5
Using the protoc-gen-openapi:
protoc-gen-openapi
message Foobar { repeated string domains = 1 [ (openapi.v3.property).items.schema_or_reference = { schema: { format: "hostname"; } } ]; }
output OpenAPI yaml:
Foobar: type: object properties: domains: type: array items: - type: string - format: hostname
Expected:
Foobar: type: object properties: domains: type: array items: type: string format: hostname
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Related to #83, #84
After the PR was merged, it was rolled back in this commit:
540b249#diff-38bb6d02d3442ac95d8613ef4fed0b1cb70f7bc2001d1abe71bafbede04a0dd1
As the comments in the latest code say, I also agree that the wrong model is being used.
gnostic/surface/model_openapiv3.go
Lines 386 to 397 in ad271d5
Using the
protoc-gen-openapi
:output OpenAPI yaml:
Expected:
The text was updated successfully, but these errors were encountered: