Add protovalidate proto to build step #141
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tstirrat15
force-pushed
the
fix-protovalidate-dependencies
branch
from
bac1fe5 to
015abc5
Compare
tstirrat15
force-pushed
the
fix-protovalidate-dependencies
branch
from
015abc5 to
a18b58d
Compare
miparnisari
approved these changes
Aug 27, 2025
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Since the last time
authzed-java's API defs were updated, we added protovalidate to the definitions. This should make for a better experience validating protos in client code, but also requires additional proto to be brought in for the build step. You can see the errors that we hit here.Changes
--exclude-importsand letting buf take care of thingsTesting
Review