The latest version of arktype is now 2.0.0-dev.14, which is consistent with an upcoming major release.
I've created a new major version of the @hookform/resolvers/arktype to match this.
I did have a question as to whether it was okay to resuse the existing errors.byPath property with a type alias for code as FieldErrors. It would have many additional properties users could introspect, so long as nowhere in hookform is there an assumption that there are no extra properties on that object (as can be seen by the snapshots with many additional properties).
If extra properties are problematic, I can adjust the code to just include message and type as they did before.
The
latest
version ofarktype
is now2.0.0-dev.14
, which is consistent with an upcoming major release.I've created a new major version of the
@hookform/resolvers/arktype
to match this.I did have a question as to whether it was okay to resuse the existing
errors.byPath
property with atype
alias forcode
asFieldErrors
. It would have many additional properties users could introspect, so long as nowhere in hookform is there an assumption that there are no extra properties on that object (as can be seen by the snapshots with many additional properties).If extra properties are problematic, I can adjust the code to just include
message
andtype
as they did before.