Support ajv-errors for precompiled schemas

[thesnups]

Prerequisites

• I have read the documentation

What theme are you using?

chakra-ui

Describe the solution you'd like

Requesting support for enabling https://ajv.js.org/packages/ajv-errors.html when using compileSchemaValidators and compileSchemaValidatorsCode. These functions support enabling ajv-formats and custom formats, but do not support ajv-errors or other custom keywords. This feature is already supported for runtime-compiled validators via customizeValidator.

[heath-freenome]

@thesnups You should be able to pass all the same AJV configuration options when you compile the schema validators using the compileSchemaValidators() via the optional third param, options the same as when you setup the runtime validator

[thesnups]

compileSchemaValidators() also doesn't support ajv-errors. It's supported by the runtime validator because you can get access to the raw AJV instance:

const validator = customizeValidator();
ajvErrors(validator.ajv);

None of the precompilation APIs give access to the raw instance like this. Access to the raw instance is needed in order to call ajv.addKeyword on it (which is what ajv-errors does)

[heath-freenome]

@thesnups Got it. Did you want to make a PR that adds support for invoking AJV Errors, by adding it as an optional parameter to the CustomValidatorOptionsType interface as follows:

export interface CustomValidatorOptionsType {
... what already there
  /** A function to call to extend AJV, such as `ajvErrors()` */
  extenderFn: (ajv: Avj) => Ajv;

And then you can update createAjvInstance() to check if there is an extenderFn() and then call it. Doing that will automatically cause the extender function to be call for both run-time as well as the compiled version.

[heath-freenome]

@thesnups Does your thumbs up mean you are working on the new feature?

[thesnups]

Yes, sorry for the ambiguity. I haven't had time yet but give me the weekend to get a PR out

[heath-freenome]

@thesnups Looking forward to getting the PR in before we ship v6 in October

[7908837174]

I'd like to work on this issue because I specialize in reproducible workflows and infrastructure clarity across TypeScript and backend systems. I’ve contributed to post-quantum cryptography tooling and standardized plugin naming in Veraison, so I’m comfortable extending validator interfaces and ensuring spec-compliant integration.

Plan of Action:

Extend CustomValidatorOptionsType to accept an extenderFn for AJV customization.

Update createAjvInstance() to invoke extenderFn(ajv) if provided.

Validate compatibility with both runtime and precompiled validators.

Add tests for ajv-errors integration and update documentation accordingly.