tractorcow

or conversely if the developer has to deal with locale code + locale ID as a identifier everywhere, does it make sense either?

tractorcow

if the developer can't create multiple variants for a locale, does it make sense to limit that developer?

tractorcow

If the user can't create a locale that already exists, does it make sense to that user?

tractorcow

I want to consider both the developer and the user here 🙂

nightjarnz

🤔 I'll put it on the GitHub issue too, but I feel like even if it isn't highly requested, this might be a case of "what feels more intuitive for a user?"

nightjarnz

yes I suppose language is confusing in this instance - locale the data object as opposed to locale, the secondary two letters on an identifier - the Y's in xx_YY

tractorcow

so if you have a global locale, you don't HAVE to pick "en_CA" or something odd 😛