You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
protovalidate-go functions with v0.3.2 but does not function with v0.3.3.
Expected Behavior
Even if the buf module version of protovalidate is old, protovalidate-go@v0.3.3 and later will function.
Actual Behavior
When the version of the buf module in protovalidate is commit 998a6885b3f74d08847b9c24571fdf08 and protovalidate-go is at v0.3.3, protovalidate-go does not function.
In #57, the resolver was improved to handle dynamically created
descriptors and inconsistent types but silently broke resolving the
deprecated version of the protovalidate extension (introduced in
[protovalidate
v0.2.0](bufbuild/protovalidate@v0.1.15...v0.2.0)).
This patch dries up the resolver a bit and fixes the (albeit deprecated)
behavior.
Fixes#116
Description
resolveDeprecatedIndex() isn't functioning.
In my project, the version of the buf module in protovalidate was fixed to commit 998a6885b3f74d08847b9c24571fdf08 in buf.lock.
Commit 998a6885b3f74d08847b9c24571fdf08 has an old extension field number of 51071.
Even so, protovalidate-go was functioning up to v0.3.2, but stopped working from v0.3.3.
I suspect the cause is in #57.
Steps to Reproduce
buf mod update
buf generate
Expected Behavior
Even if the buf module version of protovalidate is old, protovalidate-go@v0.3.3 and later will function.
Actual Behavior
When the version of the buf module in protovalidate is commit 998a6885b3f74d08847b9c24571fdf08 and protovalidate-go is at v0.3.3, protovalidate-go does not function.
Screenshots/Logs
Nothing.
Environment
Possible Solution
I suspect the cause is in #57.
Additional Context
Nothing.
The text was updated successfully, but these errors were encountered: