Enums are ALWAYS sorted

[patrickdejong]

As shown in the image below:

Enums will always be sorted on their name alphabetically. This will lead to unexpected behaviour with values being swapped.

enum RandomDay{
Monday,
Tuesday,
Friday,
Sunday
}

will become:

enum RandomDay{
Friday,
Monday,
Sunday,
Tuesday
}

So the values do not match anymore. Could you make it an option to enable the alphabetic sorting?

[marcselman]

Yeah, we saw this as well.
The generated code does not match the schema.

Source can be found here:

quicktype/packages/quicktype-core/src/ConvenienceRenderer.ts

Line 707 in 9b570a7

protected forEachEnumCase(

Related: #1289

[schani]

Triage sweep note (systematic issue-backlog triage, assisted by Claude): confirmed reproducible on current master (v23.3.0, 68ecb284).

Repro

$ cat day.schema.json
{"$schema":"http://json-schema.org/draft-07/schema#","type":"string","enum":["Monday","Tuesday","Friday","Sunday"]}

$ quicktype --lang csharp --src-lang schema day.schema.json
public enum DaySchemaEnum { Friday, Monday, Sunday, Tuesday };

Declaration order Monday, Tuesday, Friday, Sunday becomes alphabetical Friday, Monday, Sunday, Tuesday.

Root cause: ConvenienceRenderer.forEachEnumCase (packages/quicktype-core/src/ConvenienceRenderer.ts:1007) always runs case names through mapSortBy, even though EnumType.cases preserves the source's insertion order. This helper is shared by all ~29 language renderers, so the alphabetization is universal, not C#-specific.

Assessment

• Severity: low. Generated (de)serializers match enum members by string name, so JSON round-tripping is unaffected. What breaks is anything relying on positional/ordinal semantics — e.g. C#'s implicit underlying int values — plus unnecessary diff noise when a schema's enum order changes.
• Difficulty: moderate. The core fix (iterate cases in insertion order) is a small change, but doing it right means: deciding whether to make it opt-in via a new renderer option (as requested) or just fix behavior outright, updating golden fixtures across every language, and deciding how to order enums inferred from multiple JSON samples (no inherent "declaration order" there).