Deprecated Storybook addon that throws migration errors directing users to the new package structure in Storybook 9.0
86
{
"context": "This criteria evaluates the engineer's proficiency in using Storybook's event system, specifically the channel-based event communication API. The focus is on proper usage of the @storybook/channels API for event listening and the @storybook/core-events module for event type constants.",
"type": "weighted_checklist",
"checklist": [
{
"name": "Channel usage",
"description": "Uses the channel parameter correctly to register event listeners, calling channel methods such as `on()` or `addListener()` to subscribe to events.",
"max_score": 25
},
{
"name": "Event type constants",
"description": "Imports and uses event type constants from @storybook/core-events (e.g., STORY_RENDER_PHASE_CHANGED, STORY_RENDERED, UPDATE_STORY_ARGS, STORY_THREW_EXCEPTION or similar predefined event constants) instead of hard-coded strings.",
"max_score": 25
},
{
"name": "Event listener implementation",
"description": "Implements event listener callbacks that properly handle event data and update internal state (counters) when events are received.",
"max_score": 20
},
{
"name": "Statistics tracking",
"description": "Maintains an accurate data structure (e.g., Map or object) to track event counts and returns it correctly via the getStatistics() function.",
"max_score": 15
},
{
"name": "Cleanup mechanism",
"description": "Implements cleanup functionality using channel methods such as `off()` or `removeListener()` to properly unsubscribe from all registered event listeners.",
"max_score": 15
}
]
}Install with Tessl CLI
npx tessl i tessl/npm-storybook--addon-backgroundsdocs
evals
scenario-1
scenario-2
scenario-3
scenario-4
scenario-5
scenario-6
scenario-7
scenario-8
scenario-9
scenario-10