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's rich contextual parameters to build a schema analyzer. The focus is on proper utilization of the seven callback parameters (schema, jsonPtr, rootSchema, parentJsonPtr, parentKeyword, parentSchema, keyIndex) to extract and organize structural information.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Uses traverse function",
"description": "Code imports and invokes the traverse function from json-schema-traverse package with correct parameters (schema and callback or options object)",
"max_score": 15
},
{
"name": "Captures jsonPtr parameter",
"description": "Implementation accesses and uses the jsonPtr parameter from the callback to track schema paths",
"max_score": 20
},
{
"name": "Captures parentJsonPtr parameter",
"description": "Implementation accesses and uses the parentJsonPtr parameter to track parent-child relationships",
"max_score": 15
},
{
"name": "Captures parentKeyword parameter",
"description": "Implementation accesses and uses the parentKeyword parameter to identify which JSON Schema keyword contains each schema",
"max_score": 15
},
{
"name": "Uses schema parameter",
"description": "Implementation accesses the schema parameter to extract schema properties like type",
"max_score": 10
},
{
"name": "Calculates depth correctly",
"description": "Implementation correctly calculates nesting depth using the contextual parameters (e.g., by counting slashes in jsonPtr or tracking depth during traversal)",
"max_score": 15
},
{
"name": "Returns required structure",
"description": "Function returns an object with the required properties: paths array (containing objects with path, type, parent, parentKeyword, depth), maxDepth, and totalSchemas",
"max_score": 10
}
]
}