Chris Roche

Hey, @hongkongkiwi! You're likely running up against the double escaping that this string is passing through. First, the string is unescaped by the protobuf compiler, then again by the CEL...

Hey, @rsylim804! There's no go module at the root of this project, so you'll need to `go get github.com/bufbuild/protovalidate/tools@latest` to get the module that contains the migrator. (The error you're...

A solution is next on our roadmap to add support for making portable rules that can be shared across multiple fields/messages. Stay tuned! Depending on the implementation, forking might work,...

Nothing concrete yet. I have been testing out some potential strategies here, but the real sticking point is getting the ergonomics right balanced with preventing mistakes that can't be caught...

Yep, it'd work across package boundaries. Essentially, the goal is for a user to define their own custom extension options on messages and/or fields and decorate that extension with protovalidate...

Hi, @StoneGod! There are currently no plans on our end to create a Ruby runtime library for protovalidate, so feel free to create one. Primarily libraries should target and pass...

Ruby support isn't planned, but we will be glad to review any PRs adding support. The best place to start is creating the test harness for ruby and then working...

Hey @NotHolst! If you're looking to explore implementing protovalidate for a language, take a look at our [contributing guidelines](https://github.com/bufbuild/protovalidate/blob/main/.github/CONTRIBUTING.md#language-support-requirements) that cover some of the expectations for an implementation. [Conformance testing](https://github.com/bufbuild/protovalidate/blob/main/docs/conformance.md)...