or run

npx @tessl/cli init
Log in

Version

Files

tile.json

rubric.jsonevals/scenario-6/

{
  "context": "Evaluates how well the solution leverages PrimeVue's localization and accessibility configuration to drive text and aria labels for the date selection control and paginated list. Checks focus on initializing locale data, updating it reactively at runtime, and respecting provided accessibility overrides instead of hardcoded strings.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Plugin locale setup",
      "description": "Registers PrimeVue from 'primevue/config' or '@primevue/core/config' with a locale object that defines month/day names, today text, and the aria/navigation strings used by the controls instead of hardcoded text.",
      "max_score": 20
    },
    {
      "name": "Locale-driven date control",
      "description": "DatePicker or Calendar pulls visible month/day labels and button text from PrimeVue.config.locale (e.g., monthNames, dayNamesShort, today) rather than inline props.",
      "max_score": 20
    },
    {
      "name": "Locale-driven paginator",
      "description": "Paginator renders navigation labels and aria strings from PrimeVue.config.locale.aria (e.g., prevPageLabel, nextPageLabel, pageLabel) without manual DOM text replacements.",
      "max_score": 20
    },
    {
      "name": "Reactive locale switching",
      "description": "Uses usePrimeVue().config or $primevue.config to swap between locale bundles at runtime (including locale.aria) so both controls update automatically.",
      "max_score": 20
    },
    {
      "name": "Accessibility overrides",
      "description": "Merges provided override values into PrimeVue.config.locale.aria (e.g., close, prevPageLabel, nextPageLabel) instead of custom attributes, preserving other defaults.",
      "max_score": 20
    }
  ]
}