gnostic icon indicating copy to clipboard operation
gnostic copied to clipboard

A compiler for APIs described by the OpenAPI Specification with plugins for code generation and other API support tasks.

Results 125 gnostic issues
Sort by recently updated
recently updated
newest added

Is it possible to add a protobuff message to an OpenAPI schema component output? I want to have a way to add a reference for an error case like 403....

Syncing to version 0.70 with the latest go/protoc and then building, fails. ``` gnostic % make go generate ./... go get ./... go: module github.com/golang/protobuf is deprecated: Use the "google.golang.org/protobuf"...

## body (success) ```code // .proto // CreateTest rpc CreateTest(CreateTestRequest) returns (CreateTestReply) { option (openapi.v3.operation) = { summary : "CreateTest", }; option (google.api.http) = { post : "/test" body: "*"...

1. [escape](https://github.com/google/gnostic/blob/main/jsonwriter/writer.go#L29) only handle `\n` and `"` `\` should be escape also because some comment description contains it 2. [scalar write](https://github.com/google/gnostic/blob/main/jsonwriter/writer.go#L86) does not handle `!!null` and it would cause empty...

It looks like the changes merged in #367 generate duplicate `operationId`'s. You can see this in the test example: * https://github.com/google/gnostic/blob/3751138311725a0e9d353b805b2e121c94155d18/cmd/protoc-gen-openapi/examples/tests/additional_bindings/openapi.yaml#L13 * https://github.com/google/gnostic/blob/3751138311725a0e9d353b805b2e121c94155d18/cmd/protoc-gen-openapi/examples/tests/additional_bindings/openapi.yaml#L37 According to the spec these must be...

你们的v0.7.0 貌似有问题, 更新之后生成的字段, int64 全变成了string

**Issue Summary:** I am experiencing a problem with the Gnostic library and the protoc-gen-openapi plugin when generating an OpenAPI specification from a Protocol Buffer service. The generated OpenAPI specification is...

fixes #392 Before fixing this issue, if `fq_schema_naming = false` and there were duplicates of schema names traversed and formatted from all imported proto files, the wrong message could be...

use yaml type tag `!!str` to represent boolean-like and `NULL` enum values. fixes: #407