protoc-gen-validate
jsonpointer
protoc-gen-validate | jsonpointer | |
---|---|---|
6 | 3 | |
3,642 | 11 | |
0.7% | - | |
8.0 | 0.0 | |
10 days ago | over 1 year ago | |
Go | Go | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
protoc-gen-validate
- Protobuf Schema Validation
-
Protobuf-ES: The Protocol Buffers TypeScript/JavaScript runtime we all deserve
My understanding is that the powers that be within Google have decided that validating messages is outside the scope of schemas and serialization. protoc-gen-validate provides a portable way to perform validation: https://github.com/bufbuild/protoc-gen-validate
The problem with required fields is it kicks the can down the road when you want to deprecate a field. Keeping everything optional is much, much better for everyone in the long run.
-
Why isn't gRPC used more for browser to api transport over REST / graphql?
I built a (go) very rough draft to support 3.1 + a json pointer pkg to support a refactor that was in progress before I bailed on the idea. The amount of effort to get a conventional API was dwarfing that of grpc, especially with protoc-gen-validate.
- Protoc-Gen-Validate (PGV)
-
is there any package to generate validation code for struct instead of using reflect (tags)?
Yes, I am currently using this. I prefer something like this https://github.com/envoyproxy/protoc-gen-validate
-
sneak peak: code generation extensions to prost (protobuf code generator)
We've been using Rust with protobuf, but had to write lots of conversions from protobuf struct to actual DTO, since prost generates Options for nested types, and does not really support custom types. So I extended prost with the options that we needed. I might aim to also support protoc-gen-validate.
jsonpointer
-
jsonptr: JSON Pointers (RFC 6901) for Rust
I have a go implementation as well: https://github.com/chanced/jsonpointer
- JSON Pointers (rfc 6901) package
-
Why isn't gRPC used more for browser to api transport over REST / graphql?
I built a (go) very rough draft to support 3.1 + a json pointer pkg to support a refactor that was in progress before I bailed on the idea. The amount of effort to get a conventional API was dwarfing that of grpc, especially with protoc-gen-validate.
What are some alternatives?
buf - The best way of working with Protocol Buffers.
openapi - an OpenAPI 3.x library for go
prototool - Your Swiss Army Knife for Protocol Buffers
sqlx - 🧰 The Rust SQL Toolkit. An async, pure Rust SQL crate featuring compile-time checked queries without a DSL. Supports PostgreSQL, MySQL, and SQLite.
prost - PROST! a Protocol Buffers implementation for the Rust Language
docs.rs - crates.io documentation generator
ozzo-validation - An idiomatic Go (golang) validation package. Supports configurable and extensible validation rules (validators) using normal language constructs instead of error-prone struct tags.
grpc-web - gRPC Web implementation for Golang and TypeScript
jsonptr - JSON Pointer (RFC 6901) implementation for Rust
protolock - Protocol Buffer companion tool. Track your .proto files and prevent changes to messages and services which impact API compatibility.
json-patch - RFC 6902 (JSON Patch) / RFC 7396 (JSON Merge Patch) implementation for Rust