Dean Karn

Because this library is pre-1.0 this is acceptable, otherwise would be a breaking change

Hey @ccpwcn , sorry to hear about this issue. Nothing should have changed that would affected these validations, especially such core ones. Is it possible to provide a simpler reproducible...

I tried really quickly to reproduce but was unable to using the below code. I even checked the git blame, the `gte` logic hasn't changed since 2023 and that was...

Do you mean this exact same code fails on your computer @nodivbyzero ? What version of Go and OS are you using, I was using: - Go v1.24.2 - Macos...

I am confused, the original bug report stack trace shows the gte validation erroring which is only on the inner struct. I see now though why it would fail, this...

> But, I look it again, my code no problem!!! min, max options used on slice, gte used on int64, oneof used on int8. But the current definition is not...

@zemzale is correct, there is no current way to control this. This was a necessary design decision around correctness that needed to be made as the struct is only pseudo...

I'm going to have to think about this one because tags are for validation or guiding validation but this adds in a new paradigm where tags outside of validations themselves...

Hey @ralekseenkov sorry for the lateness of my reply, This library mostly intends for you the user to create your own error messages, and why `FieldError` contains so much detail;...

@ralekseenkov I see what you mean now, yes currently there is no way to do this; but it would be a great enhancement! I will add it to the improvements...