[utkarshpatwa393-sys]

Summary

Resolves #162.

When an Ajv schema specifies const: "foo" and validation fails on a mismatch, Ajv provides params: { allowedValue: "foo" }. Previously, better-ajv-errors did not handle the const keyword specifically, falling back to DefaultValidationError which output generic text: const must be equal to constant without showing what the expected constant value was.

Changes

1. Types (src/types.ts):
   • Added ConstParams type ({ allowedValue: unknown }).
2. Utils & Helpers (src/utils.ts, src/helpers.ts):
   • Added isConstError type guard.
   • Grouped const errors into enum bucket and routed them through EnumValidationError with allowedValues: [error.params.allowedValue].
3. Enum Validation Error (src/validation-errors/enum.ts):
   • Distinguishes const keyword to render CONST header (instead of ENUM).
   • Displays CONST must be equal to constant (<allowedValue>) and provides fallback pointer message Unexpected value, should be equal to constant <allowedValue> or Levenshtein suggestion if closest match found.
4. Testing & Changeset:
   • Added unit tests in src/__tests__/index.ts verifying CLI and JS formatted error outputs.
   • Added changeset in .changeset/const-error-display.md.

[changeset-bot]

🦋 Changeset detected

Latest commit: 7411b46

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[utkarshpatwa393-sys]

@torifat Hi! Resolves #162 by displaying the expected constant value for const validation errors along with suggestions and code frames. All 82 tests, build, lint, and changeset passing. Ready for your review whenever convenient!