Format JavaScript Standard Style as Stylish (i.e. snazzy) output
94
{
"context": "This evaluation assesses the engineer's ability to use the snazzy package for JSON parsing and data processing of linter output. The criteria focuses on proper utilization of snazzy's standard-json parsing capabilities and data structure handling.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Uses standard-json parser",
"description": "Uses the standard-json library (via snazzy's approach) with the `{ noisey: true }` option to parse compact linter JSON input, demonstrating knowledge of snazzy's JSON normalization approach",
"max_score": 30
},
{
"name": "Processes result structure",
"description": "Correctly iterates through the array of result objects and accesses the `filePath` and `messages` properties from each result, matching snazzy's data structure expectations",
"max_score": 20
},
{
"name": "Extracts message fields",
"description": "Extracts individual message properties (`line`, `column`, `message`, `ruleId`) from the messages array within each result, demonstrating understanding of snazzy's message structure",
"max_score": 20
},
{
"name": "Handles default values",
"description": "Provides default values for missing optional fields: line defaults to 0, column defaults to 0, and ruleId defaults to empty string, following snazzy's default value handling pattern",
"max_score": 15
},
{
"name": "Filters empty results",
"description": "Skips or appropriately handles files with no linting errors (empty messages arrays), similar to how snazzy filters results",
"max_score": 10
},
{
"name": "Aggregates error counts",
"description": "Calculates the total number of problems across all files by counting messages, demonstrating understanding of snazzy's error count aggregation",
"max_score": 5
}
]
}Install with Tessl CLI
npx tessl i tessl/npm-snazzydocs
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10