Converts HTML entities to their corresponding characters in a string
Overall
score
85%
Evaluation — 85%
↑ 1.39xAgent success when using this tile
{
"context": "This criteria evaluates how well the engineer uses lodash's object property enumeration functions (keys, values, entries, keysIn, valuesIn) to implement a configuration manager. The focus is on proper usage of these specific lodash methods rather than native JavaScript alternatives.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Uses _.keys",
"description": "Uses lodash's _.keys() function to implement getConfigKeys() instead of Object.keys() or other alternatives",
"max_score": 20
},
{
"name": "Uses _.values",
"description": "Uses lodash's _.values() function to implement getConfigValues() instead of Object.values() or other alternatives",
"max_score": 20
},
{
"name": "Uses _.entries",
"description": "Uses lodash's _.entries() or _.toPairs() function to implement getConfigEntries() instead of Object.entries() or manual iteration",
"max_score": 20
},
{
"name": "Uses _.keysIn",
"description": "Uses lodash's _.keysIn() function to implement getAllKeys() to include inherited properties, not just _.keys()",
"max_score": 25
},
{
"name": "Proper filtering implementation",
"description": "Uses lodash functions like _.pickBy() or _.pick() combined with _.keys() or _.values() to implement type-based filtering in filterByValueType()",
"max_score": 15
}
]
}Install with Tessl CLI
npx tessl i tessl/npm-lodash-unescapedocs
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10