Fix mismatched example in sint32 and int64 suites (#245)

In theory this is not a big deal, but the Go implementation actually catches this, since it validates which standard constraints you use. (I feel we should probably include that check in `buf lint` as well since presumably we don't yet.)
bufbuild · Sep 4, 2024 · 3edb475 · 3edb475
1 parent 39747ae
commit 3edb475
Show file tree

Hide file tree

Showing 2 changed files with 376 additions and 376 deletions.
diff --git a/proto/protovalidate-testing/buf/validate/conformance/cases/numbers.proto b/proto/protovalidate-testing/buf/validate/conformance/cases/numbers.proto
@@ -338,7 +338,7 @@ message Int64IncorrectType {
 }
 
 message Int64Example {
-  int64 val = 1 [(buf.validate.field).float.example = 10];
+  int64 val = 1 [(buf.validate.field).int64.example = 10];
 }
 
 message UInt32None {
@@ -557,7 +557,7 @@ message SInt32IncorrectType {
 }
 
 message SInt32Example {
-  sint32 val = 1 [(buf.validate.field).int32.example = 0];
+  sint32 val = 1 [(buf.validate.field).sint32.example = 0];
 }
 
 message SInt64None {