Skip to content

feat: support extensible enum values - #2847

Closed
sb123sb123 wants to merge 1 commit into
Redocly:mainfrom
sb123sb123:feat/461-extensible-enum
Closed

sb123sb123 wants to merge 1 commit into
Redocly:mainfrom
sb123sb123:feat/461-extensible-enum

Conversation

@sb123sb123

Copy link
Copy Markdown

Closes #461

Summary

Use array-valued x-extensible-enum and other x-*-enum schema extensions as display enum values. Standard enum remains authoritative when both forms are present, and extensions on array item schemas are handled as well.

Validation

  • npm run unit -- --runInBand --no-coverage --runTestsByPath src/services/tests/models/Schema.test.ts — 35 passed, 12 snapshots passed.
  • npm run ts-check — passed.
  • ESLint on both changed files — passed.
  • Prettier check and git diff --check — passed.

Signed-off-by: NekoPaw <152394158+sb123sb123@users.noreply.github.com>
@sb123sb123
sb123sb123 requested a review from a team as a code owner October 6, 2026 16:57
@AlexVarchuk

Copy link
Copy Markdown
Collaborator

@sb123sb123 Thanks for the contribution, and apologies that we didn't get to this in time. 🙏

We've released Redoc v3.0.0 with major changes, so we're closing PRs opened against the old version. If this is still relevant for v3, feel free to rebase onto main and reopen it, and we'll review it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Support x-extensible-enum (and other x-enum if possible)

2 participants