Ability to add label to be shown in error instead of generic like: String must contain at least 3 character(s)

For example if I have this validation

const schema = z.object({
   firstName: z.string().min(3).max(12),
   isActive: z.boolean(),
   role: z.enum(['Admin', 'User']),
});

const result = schema.safeParse({
   "firstName": '',
   "isActive": null,
   "role": "min",
});

console.log(JSON.stringify(result, null, 2));

{
  "success": false,
  "error": {
    "issues": [
      {
        "code": "too_small",
        "minimum": 3,
        "type": "string",
        "inclusive": true,
        "message": "String must contain at least 3 character(s)",
        "path": [
          "firstName"
        ]
      },
      {
        "code": "invalid_type",
        "expected": "boolean",
        "received": "null",
        "path": [
          "isActive"
        ],
        "message": "Expected boolean, received null"
      },
      {
        "received": "min",
        "code": "invalid_enum_value",
        "options": [
          "Admin",
          "User"
        ],
        "path": [
          "role"
        ],
        "message": "Invalid enum value. Expected 'Admin' | 'User', received 'min'"
      }
    ],
    "name": "ZodError"
  }
}

Error message will be

firstName must contain at least 3 character(s) instead of String must contain at least 3 character(s)

[ITwrx]

i think by default it should use the field name, and also have a convenient override like label().

[ITwrx]

so it seems like you’re asking why users can’t just use path as alluded to in the ERROR_HANDLING docs. There is also this package as another option.

IIRC, (i haven’t used any of this in 2 months) I think some of us just didn’t see why manual customization/workaround or another package should be necessary to use path by default and preferably even a label() option. If it needs to stay hard-coded with a generic type label for other use cases, then that’s understandable.

If what i have listed above is the stance of devs, than maybe closing as wontfix, optionally with a brief explanation, would be preferable to the stalebot being unleashed, which i find to be a somewhat disagreeable way to close an issue. 😃

thanks