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 understanding and proper usage of picomatch's globstar (**) pattern matching capability for recursive directory traversal. The focus is on correctly utilizing picomatch functions to match file paths across multiple directory levels.",
"type": "weighted_checklist",
"checklist": [
{
"name": "picomatch import",
"description": "Code imports picomatch (either the main picomatch function, picomatch.isMatch, or picomatch.makeRe) from the 'picomatch' package",
"max_score": 10
},
{
"name": "Globstar pattern usage",
"description": "Code correctly uses the globstar (**) pattern in conjunction with picomatch to match files across multiple directory levels (e.g., patterns like '**/*.js', 'tests/**/*.test.js', or '**/User*.js')",
"max_score": 25
},
{
"name": "Path construction",
"description": "Code properly constructs file paths by traversing the nested object structure and building complete paths with forward slashes as separators",
"max_score": 20
},
{
"name": "Pattern matching integration",
"description": "Code uses picomatch functions (such as picomatch(), picomatch.isMatch(), or a compiled matcher) to test constructed file paths against the provided pattern",
"max_score": 25
},
{
"name": "Recursive traversal",
"description": "Code implements recursive directory traversal that explores the entire file tree structure to find all matching files at any nesting level",
"max_score": 15
},
{
"name": "Correct output",
"description": "Function returns sorted array of matching file paths for all three test cases, correctly identifying files that match the globstar patterns",
"max_score": 5
}
]
}