Add isIpPrefix

[higebu]

• protovalidate-go: Add isIpPrefix protovalidate-go#53
• protovalidate-cc: Add isIpPrefix protovalidate-cc#45 (via @paina)
• protovalidate-java: Add isIpPrefix protovalidate-java#39
• protovalidate-python: Add isIpPrefix protovalidate-python#78

[CLAassistant]

All committers have signed the CLA.

[rodaine]

Hi @higebu! Thanks for taking the time to so thoroughly implement this. Have you had a chance to look at the previous discussion on including support for CIDR blocks in the linked issue?

[higebu]

Hi @rodaine! Thank you for taking a look. Sure. I'll check the issue.

[paina]

Hi @rodaine, @higebu.
I've PR-ed C++ implementation of isIpPrefix() as bufbuild/protovalidate-cc#45.
If it works, we will be able to use the validation with C++.

[rodaine]

Looking good! Can you please add some conformance tests to ensure that they're correctly handling these new constraints?

• Case proto definitions: https://github.com/bufbuild/protovalidate/tree/main/proto/protovalidate-testing/buf/validate/conformance/cases
• And where you define a suite of tests: https://github.com/bufbuild/protovalidate/tree/main/tools/protovalidate-conformance/internal/cases

You can either add this to the existing strings suite or create a new one specifically for this new rule.

[higebu]

@rodaine Thank you for the guidance of conformance tests. I added some conformance tests and will fix protovalidate-xxx.

[higebu]

@rodaine I fixed protovalidate-python and protovalidate-java with conformance tests.
bufbuild/protovalidate-python#78 (comment)
bufbuild/protovalidate-java#39 (comment)

BTW, how to run protovalidate-conformance with protovalidate-go and protovalidate-cc? They seems to depends on bufbuild/[email protected], so I can't not test with development version of protovalidate.

[rodaine]

Hey @higebu! Going to start merging these so you should be able to update the conformance tests for the libraries downstream.