Are custom error messages no longer allowed?

[jtlapp]

It appears that the message option no longer exists to override the hardcoded error messages. Is this correct?

OLD POST:

I created the following type:

export const IntegerString = TypeSystem.Type<
  string,
  { minimum?: number; maximum?: number; maxDigits?: number } & SchemaOptions
>("Integer String", (options: any, value: any) => {
  if (
    typeof value !== "string" ||
    (options.maxDigits !== undefined && value.length > options.maxDigits) ||
    !/^[0-9]+$/.test(value)
  ) {
    return false;
  }
  const integer = parseInt(value);
  return (
    (options.minimum === undefined || integer >= options.minimum) &&
    (options.maximum === undefined || integer <= options.maximum)
  );
});

But I get the error message "Expected kind Integer String" for the following:

    DATABASE_PORT: IntegerString({
      minimum: 0,
      maximum: 65535,
      message: "expected a string providing an integer >= 0 and <= 65535",
    }),

Can custom types have custom error messages?

UPDATE: Wait. message is no longer working on any types, custom or not.

[jtlapp]

Never mind. I'm using this type in a type context, whereas I was previously using types in a context that wrapped validation and reported errors via error.schema.message ?? error.message.