You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Both descriptions of the language map pattern talk about the utility of using object.en as a method of accessing the data. However, neither mention the subsequent headache of "-region" or other BCP47 values beyond the simple two letter code for the language as a whole.
If I use "en-us" as the language of my string then I just broke everyone's dot-property notation code, as they'll try in vain to do:
text = object.occupation.en - us;
and hopefully get a 'Variable Not Defined: us' error, and at worst (if us is defined as something that can be subtracted from a string) some very badly broken content.
This should be in a note in one or both of the descriptions.
The text was updated successfully, but these errors were encountered:
Both descriptions of the language map pattern talk about the utility of using object.en as a method of accessing the data. However, neither mention the subsequent headache of "-region" or other BCP47 values beyond the simple two letter code for the language as a whole.
If I use "en-us" as the language of my string then I just broke everyone's dot-property notation code, as they'll try in vain to do:
and hopefully get a 'Variable Not Defined: us' error, and at worst (if us is defined as something that can be subtracted from a string) some very badly broken content.
This should be in a note in one or both of the descriptions.
The text was updated successfully, but these errors were encountered: