Intl.LocaleMatcher ponyfill providing comprehensive locale matching algorithms with support for 'lookup' and 'best fit' strategies
94
{
"context": "This criteria evaluates how effectively the engineer uses @formatjs/intl-localematcher to resolve user locale preferences with Unicode extension support. The focus is on proper usage of ResolveLocale function and related locale resolution capabilities.",
"type": "weighted_checklist",
"checklist": [
{
"name": "ResolveLocale usage",
"description": "Uses the ResolveLocale function from @formatjs/intl-localematcher as the primary mechanism for locale resolution with extension handling",
"max_score": 30
},
{
"name": "Extension key processing",
"description": "Correctly passes relevantExtensionKeys parameter to enable Unicode extension processing (calendar, numbering system, hour cycle)",
"max_score": 15
},
{
"name": "Locale data integration",
"description": "Properly provides and structures localeData parameter containing supported extension values for validation",
"max_score": 15
},
{
"name": "Options override handling",
"description": "Correctly implements priority order where user options override extension keywords by passing options parameter to ResolveLocale",
"max_score": 15
},
{
"name": "Result structure extraction",
"description": "Properly extracts and returns both locale (with extensions) and dataLocale (for data lookups) from ResolveLocale result along with extension property values",
"max_score": 15
},
{
"name": "Basic locale matching",
"description": "Uses appropriate locale matching (via ResolveLocale's internal matching or explicit match function) to resolve requested locales against available locales",
"max_score": 10
}
]
}Install with Tessl CLI
npx tessl i tessl/npm-formatjs--intl-localematcherdocs
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10