You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently while generating openapi v3 yaml specification:
For path-variables and request-parameters, there is no handling for field schema properties
If one wants to add more control on path variable, (such as regex pattern), the property(openapi.v3.property option) will be ignored. (just create the plain schema), the problem is it might not meet standard owasp criteria as a openapi v3 document.
Should the expected behavior be like how message body handling it? - that besides above, also finding the customized property then merge with current schema
Hello,
Currently while generating openapi v3 yaml specification:
For path-variables and request-parameters, there is no handling for field schema properties
If one wants to add more control on path variable, (such as regex pattern), the property(openapi.v3.property option) will be ignored. (just create the plain schema), the problem is it might not meet standard owasp criteria as a openapi v3 document.
code:
gnostic/cmd/protoc-gen-openapi/generator/generator.go
Line 470 in ad271d5
Should the expected behavior be like how message body handling it? - that besides above, also finding the customized property then merge with current schema
gnostic/cmd/protoc-gen-openapi/generator/generator.go
Line 870 in ad271d5
The text was updated successfully, but these errors were encountered: