Skip to content

Add --no-enum-sort flag to preserve spec-defined enum order#300

Merged
miniBill merged 1 commit intowolfadex:mainfrom
zupo:feat/no-enum-sort
Apr 20, 2026
Merged

Add --no-enum-sort flag to preserve spec-defined enum order#300
miniBill merged 1 commit intowolfadex:mainfrom
zupo:feat/no-enum-sort

Conversation

@zupo
Copy link
Copy Markdown
Contributor

@zupo zupo commented Apr 15, 2026

By default, enum variants are sorted alphabetically. Passing --no-enum-sort preserves the order defined in the OpenAPI spec, which is useful when enum order is meaningful (e.g. status workflows).

@zupo zupo force-pushed the feat/no-enum-sort branch 7 times, most recently from 9fb4780 to 509af79 Compare April 16, 2026 16:36
Copy link
Copy Markdown
Collaborator

@miniBill miniBill left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some small details, feel free to ignore the ones marked as nitpick.

Comment thread src/CliMonad.elm Outdated
Comment thread src/CliMonad.elm Outdated
Comment thread tests/Test/OpenApi/Generate.elm
Comment thread tests/Test/OpenApi/Generate.elm Outdated
@zupo zupo force-pushed the feat/no-enum-sort branch 2 times, most recently from d4a8bfc to d323125 Compare April 17, 2026 13:55
By default, enum variants are sorted alphabetically (existing behaviour).
Passing --no-enum-sort preserves the order defined in the OpenAPI spec,
which is useful when enum order is meaningful (e.g. status workflows).
@zupo zupo force-pushed the feat/no-enum-sort branch from d323125 to ad64fbb Compare April 17, 2026 13:56
@miniBill miniBill merged commit 1121fcb into wolfadex:main Apr 20, 2026
1 of 2 checks passed
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.

2 participants