Node errors for locale display names to 'unsupported' #319
Conversation
|
Fixes #318 |
| if (error instanceof RangeError) { | ||
| // The locale can't be handled for some reason! | ||
| outputLine["error_type"] = 'unsupported'; | ||
| outputLine["unsupported"] = error.toString(); | ||
| outputLine["error_detail"] = 'unsupported locale'; | ||
| } |
There was a problem hiding this comment.
error instanceof RangeError seems a bit broad. I suggest a narrower case for returning unsupported.
There was a problem hiding this comment.
Hmm, there are two types of failures right now. Here's what I see being caught as exceptions:
- Unexpected options in the locale spec, e.g., "label":"0009","language_label":"en-u-nu-deva-t-de","locale_label":"en"
--> "RangeError: invalid_argument"
- "root" locale --> "RangeError: invalid_argument" in the constructor.
Should either of these be "unsupported"?
There was a problem hiding this comment.
I think classifying these as "unsupported" is correct. This will resolve a large number of "errors" --> "unsupported", i.e.,
Report created: 2024-10-07 10:36
1,990 attempted. Pass: 1,460, Fail: 214, Errors: 316, Unsupported: 0
|
I've updated this to categorize unsupported locale options as "Unsupported". This reduces errors and failures. I think this is worth submitting. PTAL. |
This fixes all the "error" cases in NodeJs for locale display names, moving them to "unsupported". This works for unsupported locale options and also the "root" locale.