evals
scenario-1
scenario-10
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
{
"context": "This criteria evaluates how well the engineer uses jsdoc-to-markdown to implement multi-pass rendering workflows, specifically assessing their ability to parse documentation data once and efficiently reuse it to generate multiple output formats with different styling options.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Template data extraction",
"description": "Uses getTemplateData() method to extract and parse JSDoc data once from the source files, storing the result for reuse across multiple renders",
"max_score": 30
},
{
"name": "Verbose format rendering",
"description": "Uses render() method with the template data and options { 'heading-depth': 2, 'separators': true } to generate the verbose documentation format",
"max_score": 20
},
{
"name": "Compact format rendering",
"description": "Uses render() method with the template data and options { 'heading-depth': 3, 'separators': false } to generate the compact documentation format",
"max_score": 20
},
{
"name": "Table format rendering",
"description": "Uses render() method with the template data and options { 'heading-depth': 2, 'param-list-format': 'table' } to generate the table format documentation",
"max_score": 20
},
{
"name": "Efficient data reuse",
"description": "Passes the same template data (via the 'data' option) to render() for all three formats instead of re-parsing source files, demonstrating understanding of the multi-pass workflow pattern",
"max_score": 10
}
]
}