{{ message }}
Repository navigation
Tags: higebu/protovalidate-java
Tags
Improve protovalidate overloads (bufbuild#36) Update all of the protovalidate overload functions to add proper type checking and return Err.noSuchOverload if the types are incorrect. Greatly simplify the unique implementation as it didn't need to support non-list arguments. Fix a bug in the unique implementation for bytes (if the bytes contained invalid UTF-8). Add testcases for unique and additional tests for invalid arguments. Update Format.format to use exceptions for control flow instead of having to distinguish Val.Err from other types (a lot of places were just returning null). Remove all places where we used '==' to compare object type instances with comparing using enum types (which is safe for '==' comparison).
Include AST issues display string in compilation error (bufbuild#14) Including the errors from the compiler makes it easier to find and fix errors. For example this signed-versus-unsigned type error: ``` build.buf.protovalidate.exceptions.CompilationException: Failed to compile expression id.non_zero: ERROR: <input>:1:28: found no matching overload for '_!=_' applied to '(uint, int)' | this.most_significant_bits != 0 || this.least_significant_bits != 0u | ...........................^ ```
Fix ValidationResult#isSuccess() when result is success (bufbuild#27) Is this just a bug? expected: violations.isEmpty() => validation is success current: violations.isEmpty() => validation is **not success** I think so according to this example. https://github.com/bufbuild/protovalidate-java#example --------- Co-authored-by: Philip K. Warren <pkwarren@users.noreply.github.com> Co-authored-by: Philip K. Warren <pwarren@buf.build>
Upgrade to v0.4.2 (bufbuild#25) depends on bufbuild/protovalidate#82
Fix remote generation usage conflicts (bufbuild#13) Locally generating and packaging protovalidate protos in this repo. Fixes: bufbuild/protovalidate#62 --------- Co-authored-by: Philip K. Warren <pkwarren@users.noreply.github.com>
