Michael Shilman

@ndelangen the repro generation is failing because it uses `yarn bootstrap --prep` and that fails on the angular examples with errors like this: ``` > nx run @storybook/angular:prep --reset ERR!...

@ntindle Blazor isn't currently on our dev roadmap. However, it's possible to add framework support yourself, and this is documented here: https://storybook.js.org/docs/react/api/new-frameworks We also have a Discord community for interactive...

i know next to nothing about blazor, but i'll share a couple pieces of info in case anybody finds it useful: 1. we have no plans to support blazor in...

@dgcaron What would supporting WebAssembly entail? That sounds like something we'd want to do, but I'd need to learn more.

@Gieted I like the proposal, but I need a few days to let it roll around in my head. Thanks for thinking the problem through and being patient about this!

What do you think about this as a workaround: https://github.com/storybookjs/storybook/pull/12685

By default, each field in a component's args is rendered as a single row. If a field is a complex type, it will get rendered using a JSON editor per...

@jpmarra the issue is still open, meaning that it hasn't been added to storybook yet

We'll be iterating https://github.com/storybookjs/storybook/pull/12824 and releasing in 6.2 as a short-term improvement in this space. We definitely see value in making the destructured UI as requested here, but don't have...

Hi @joshacheson sorry I missed this! Would love to figure out what is required here. All of the interactions work runs in the browser, so it should work completely independently...