docs
evals
scenario-1
scenario-10
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
{
"context": "Evaluates whether the solution uses jsx-ast-utils to resolve JSX element names, especially via the elementType helper, when normalizing, categorizing, and summarizing elements. Focuses strictly on correct, consistent use of the package API to cover fragments, member expressions, namespaced tags, and invalid inputs.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Imports elementType",
"description": "Imports and uses jsx-ast-utils' elementType helper instead of reimplementing JSX name parsing.",
"max_score": 15
},
{
"name": "Fragment support",
"description": "Relies on elementType to return '<>' for fragments and propagates that normalized value through resolve, categorize, and summarize paths.",
"max_score": 20
},
{
"name": "Member/namespaced",
"description": "Uses elementType outputs for deeply nested member expressions (e.g., UI.Controls.Button) and namespaced tags (e.g., svg:path) without manual string assembly.",
"max_score": 25
},
{
"name": "Invalid node errors",
"description": "Leverages elementType's error behavior (or a direct call guarded only by type checks) so non-JSX nodes trigger a TypeError as specified.",
"max_score": 15
},
{
"name": "Shared normalization",
"description": "Downstream helpers (categorization and summary) reuse elementType-derived values rather than duplicating resolution logic.",
"max_score": 25
}
]
}