Is there a way to get canonical/correct casing for IANA timezone names in Luxon?

[ThatSameer]

Is your feature request related to a problem? Please describe.
I’m using Luxon to validate user-provided IANA timezone strings. Luxon’s DateTime.setZone() method correctly validates timezones case-insensitively, but it preserves the input casing when accessing zoneName.
For example, if given america/nEw_york, zoneName returns america/nEw_york instead of the canonical America/New_York.

I would've expected using toFormat('z') to return the correctly cased IANA timezone but it still returns the incorrectly cased user inputted timezone.

From what I can see, Luxon doesn't support normalise or canonicalise IANA timezone names with correct casing... unless it's me doing something wrong?

Describe the solution you'd like
To be able to normalise/canonicalise IANA timezones with correct casing

Describe alternatives you've considered
Manually correct casing comparing to IANA timezone database

[diesieben07]

You're right, Luxon should use the value the Browser gives us instead of sticking with what the user provided.

In the meantime, you can get what you want from the Intl API:

new Intl.DateTimeFormat(undefined, { timeZone: "america/nEw_york" }).resolvedOptions().timeZone; // => "America/New_York"

It should be quite easy to add this in IANAZone, considering we're already calling new Intl.DateTimeFormat there to validate that the Zone exists. I'd be happy to take a pull request for it.