docs
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 effectively the engineer uses json-schema-traverse to track parent-child relationships in JSON Schema documents. The focus is on proper usage of the traversal callback parameters (parentJsonPtr, parentKeyword, keyIndex) and leveraging the library's built-in capabilities rather than manual traversal.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Uses traverse function",
"description": "Solution imports and calls the traverse function from json-schema-traverse package to iterate through schema objects",
"max_score": 20
},
{
"name": "Uses parentJsonPtr parameter",
"description": "Solution accesses the parentJsonPtr callback parameter to capture the parent's JSON Pointer path",
"max_score": 20
},
{
"name": "Uses parentKeyword parameter",
"description": "Solution accesses the parentKeyword callback parameter to identify which keyword contains the current schema",
"max_score": 20
},
{
"name": "Uses keyIndex parameter",
"description": "Solution accesses the keyIndex callback parameter to identify the property name or array index within the parent keyword",
"max_score": 20
},
{
"name": "Uses jsonPtr parameter",
"description": "Solution accesses the jsonPtr callback parameter to capture the current schema's JSON Pointer path",
"max_score": 15
},
{
"name": "Excludes root schema",
"description": "Solution correctly filters out the root schema (where parentJsonPtr is undefined) from the results",
"max_score": 5
}
]
}