Apple's property list parser/builder for Node.js and browsers
88
Pending
Does it follow best practices?
Impact
88%
0.97xAverage score across 10 eval scenarios
Pending
The risk profile of this skill
{
"context": "This criteria evaluates how well the engineer uses the plist package to handle integer data type conversion when parsing and building Apple property list XML files. The focus is on correctly using plist.parse() and plist.build() functions to ensure whole numbers are properly represented as integers rather than floating-point numbers.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Uses plist.parse()",
"description": "The parseConfig function correctly uses plist.parse() to convert plist XML strings into JavaScript objects",
"max_score": 25
},
{
"name": "Uses plist.build()",
"description": "The generateConfig function correctly uses plist.build() to convert JavaScript objects into plist XML strings",
"max_score": 25
},
{
"name": "Integer parsing",
"description": "Correctly parses <integer> elements from plist XML into JavaScript numbers using plist.parse()",
"max_score": 20
},
{
"name": "Integer generation",
"description": "Whole numbers in JavaScript objects are correctly converted to <integer> elements (not <real>) in the generated plist XML using plist.build()",
"max_score": 20
},
{
"name": "Type distinction",
"description": "Successfully distinguishes between integers and floating-point numbers, ensuring plist.build() generates <integer> for whole numbers and <real> for decimals",
"max_score": 10
}
]
}docs
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10