Michael Shilman
Michael Shilman
@yannbf WDYT about prefixing all our env vars with `SB_` to avoid clashes?
example: in CE project, some logos took time to load which resulted in flaky snapshot tests
Issue: N/A ## What I did - [x] Update sandbox to support renderer preview annotations - [x] Copy useful stories from `examples/vue-3-cli` to Vue3 renderer - [x] Delete `examples/vue-3-cli` ##...
Issue: N/A There are a couple problems with Vue2's `renderToDom` - The element `#storybook-root` is re-created on first render, which breaks the `play` function's `within(canvas)` - Decorators that reassign args,...
Issue: N/A ## What I did - [x] web-components/vite framework - [x] JS/TS repro-templates @tmeasday Maybe this should be `lit-vite` and generate lit stories? putting the simple version up for...
https://github.com/storybookjs/storybook/issues/13913 but for Svelte This causes failures in our new framework-independent rendering stories
Our framework-independent stories use a pattern where we override args to the `Pre` component, e.g. ```js decorators: [ (storyFn: PartialStoryFn, context: StoryContext) => storyFn({ args: { object: context.argTypes } }),...
This commit removes the `app` export from `@storybook/vue3`: https://github.com/storybookjs/storybook/commit/24251e27f1233a568fd441df65af3355d89cf0f5#diff-63c4fc9feba520d3505ec8a6796e7d0576ef804b6f92d68ae8b8c2e64f18264c We should try to restore it so that users can use it to add global components and directives.
CSF3.0 introduces default render functions, making it possible to remove lots of boilerplate in your stories. The initial implementation is for React, and we still need to add this for...
Currently, addons can reference other addons by name. For example, `addon-essentials` has the following structure: ``` export const addons = async (existing) => ([...existing, '@storybook/addon-actions', ...]); ``` This matches how...