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
We are trying to migrate from protoc-gen-validate but we also apply a few patches such as validation on (google.api.field_behavior) = required, etc. Affected files that we patch in the protoc-gen-validate repository are included under templates/go/...templates/goshared/... and templates/shared/....
More specifically within the protovalidate repository is there an equivalent file that exists under protoc-gen-openapi like for templates/shared/functions.go? And generally patches that applied under these files in protoc-gen-validate is there equivalent files in the protovalidate repository?
The text was updated successfully, but these errors were encountered:
Hi, @rsylim804! While protoc-gen-validate (PGV) relied on code generation to provide validation methods, protovalidate does its job entirely at runtime with zero code generation. The only information used is what's included in your proto files themselves. The standard constraints provided by protovalidate are a superset of those you're familiar with from PGV, but also adds support for custom constraints via CEL expressions. There's work underway to make this more ergonomic for rules that are often repeated/shared across multiple fields.
We are trying to migrate from protoc-gen-validate but we also apply a few patches such as validation on (google.api.field_behavior) = required, etc. Affected files that we patch in the protoc-gen-validate repository are included under
templates/go/...
templates/goshared/...
andtemplates/shared/...
.More specifically within the protovalidate repository is there an equivalent file that exists under protoc-gen-openapi like for
templates/shared/functions.go
? And generally patches that applied under these files in protoc-gen-validate is there equivalent files in the protovalidate repository?The text was updated successfully, but these errors were encountered: