-
Notifications
You must be signed in to change notification settings - Fork 249
New issue
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
protoc-gen-openapi: google.protobuf.Duration not string #351
Comments
That seems like an oversight. We probably just need to hook up something like this. |
nightlyone
added a commit
to nightlyone/gnostic
that referenced
this issue
Aug 6, 2023
by reporting the data types and formats that are actually used TODO: * [ ] Find out why it is different than expected when durations are used in a query parameter. What parts of gnostic work different here? Fixes: google#351
nightlyone
added a commit
to nightlyone/gnostic
that referenced
this issue
Aug 6, 2023
by reporting the data types and formats that are actually used Fixes: google#351
timburks
pushed a commit
that referenced
this issue
Aug 25, 2023
by reporting the data types and formats that are actually used Fixes: #351
20 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Why is the google.protobuf.Duration converted into OpenAPI as a custom object and not as a string (the JSON format)?
I would expect it to be represented by
type: string
. Especially when the google.protobuf.Timestamp (which holds the same structure as google.protobuf.Duration) is converted into string (JSON format) as well.For instance:
is converted by protoc-gen-openapi into
See google.protobuf.Duration JSON description and google.protobuf.Timestamp JSON description for more info.
The text was updated successfully, but these errors were encountered: