nodivbyzero

@alecbakholdin Could you specify which go-errorlint linting errors you addressed in this PR?

cc: @deankarn

@deankarn I successfully reproduced this crash/panic ``` package main import ( "fmt" "github.com/go-playground/validator/v10" ) type OrderItem struct { SkuId int64 `json:"skuId,omitempty" form:"skuId" validate:"required,gte=1"` Subject int8 `json:"subject,omitempty" form:"subject" validate:"required,oneof=1 2"` Amount...

@deankarn not exactly the same. I changed `binding:"required,dive,min=1,max=100"` to `validate:"required,dive,min=1,max=100"` in the provided example. My Go version: ``` $ go version go version go1.24.1 darwin/arm64 ``` Here is the unit-test...

Sorry to hear that your team had a difficult time migrating from `v10.14`. We do our best to maintain backward compatibility with each release, and we always recommend staying up...

Overall, it looks good to me. I just have one question regarding the commented code in this PR.

@MeNavel The `unique` validation tag is designed for arrays, slices, and maps - not for single string fields. Since `NIK` is a string, the `unique=NIK` validation does not work as...

@luckv It looks like your example loops through the `tagsToTest` list, but ends up testing only the `printascii` tag. ``` if err := validate.Var(arr, "printascii"); err != nil { ```

@luckv Good catch! `isPrintableASCII` and `isASCII` do have a bug and mishandles the input as an array. A PR with a fix would be greatly appreciated.