docs
evals
scenario-1
scenario-10
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
{
"context": "This evaluation assesses how well the engineer uses the plist package's null and undefined semantic distinction capabilities. The plist package handles undefined values by omitting them from XML output, while preserving null values as explicit <null/> elements.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Uses plist.build",
"description": "Uses the plist.build() function to convert JavaScript objects to XML plist format",
"max_score": 20
},
{
"name": "Uses plist.parse",
"description": "Uses the plist.parse() function to convert XML plist strings back to JavaScript objects",
"max_score": 20
},
{
"name": "Undefined omission",
"description": "Implementation correctly relies on plist's behavior of omitting undefined values from the XML output (not manually filtering them)",
"max_score": 25
},
{
"name": "Null preservation",
"description": "Implementation correctly relies on plist's behavior of preserving null values as explicit <null/> elements in the XML output",
"max_score": 25
},
{
"name": "Correct parsing",
"description": "Implementation correctly uses plist.parse() to restore objects from XML, properly handling null elements",
"max_score": 10
}
]
}