David Dudson
David Dudson
Our company also getting the same issue. turning `storyStoryV7` on in an angular 6.5.12 project, with a decorator such as ``` componentWrapperDecorator( story => `${story}` ) ``` results in story...
Turns out this is a duplicate of https://github.com/storybookjs/storybook/issues/17330 and there is a fix is here: https://github.com/storybookjs/storybook/commit/23a3438abbde0be05631a1cbd747fa1970a26806 Because its not in the 6.X line, the best solution is to use patch-package...
That would be perfect I reckon
@MrJithil Is this still being worked on?
@olafurpg For "Universe" like behaviour I agree that we should use context. perhaps even make it implicit. For parameters specifically, they are named, and on the class that is the...
Thats fair. Although I think we will want to provide helper methods that provide clearer error messages rather then just a match error. It's a common enough pattern. I see...
@olafurpg Do you like this better than the current API?
Blocked by #24
I propose we push for at a bare minimum FQN discovery for 0.1, with the potential for semantic-db etc. being added to generator contexts for 0.2
Blocked by #21