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 the engineer's ability to use jsdoc-to-markdown's filtering capabilities to control which JSDoc elements appear in generated documentation. The focus is on proper use of the package's API for filtering by ignore tags, scope, and element kind.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Core Package Import",
"description": "Uses jsdoc-to-markdown package (typically imported as jsdoc2md or similar) to generate documentation",
"max_score": 10
},
{
"name": "Ignore Tag Filtering",
"description": "Properly filters elements marked with @ignore tags by using getTemplateData() to access parsed JSDoc data and filtering out elements where the 'ignore' property is true",
"max_score": 25
},
{
"name": "Scope-based Filtering",
"description": "Implements scope filtering (public/private/protected) by accessing the 'access' or 'scope' property from template data and filtering elements based on user-specified scope preferences",
"max_score": 25
},
{
"name": "Kind-based Filtering",
"description": "Implements kind filtering by accessing the 'kind' property from template data (e.g., 'function', 'class', 'member') and filtering elements based on user-specified kind preferences",
"max_score": 25
},
{
"name": "Pipeline Integration",
"description": "Uses render() with filtered template data or correctly chains getTemplateData() -> filter data -> render() to generate final markdown output",
"max_score": 15
}
]
}