Addon-docs: Module story format & framework param

[shilman]

Issue: #7101

What I did

This PR combines two different ideas: module story format and adding a "framework" parameter for stories. I combined the two PRs because they touch the same code and it's a pretty simple "regular" change that gets repeated across all the apps.

export default {
  title: 'Root/path/to/component'
}
export const story1 = () => <Component />
export const story2 = () => <Component something={false} />

How to test

cd examples/official-storybook
yarn storybook

Probably should add unit tests as well, and potentially convert the other examples to the new load API. Suggestions?

[vercel]

This pull request is automatically deployed with Now.
To access deployments, click Details below or on the icon next to each push.

Latest deployment for this branch: https://monorepo-git-7101-module-story-format.storybook.now.sh

[tmeasday]

Some comments

[tmeasday]

👍

[igor-dv]

I understand that passing framework will be used later (I see it already in https://github.com/storybookjs/storybook/pull/7119/files#diff-0f7bedc2d2cb7019c3fe0f0f28c18959R13). Are any other usecases to this ? (I am always standing for things to be generic =) )

[shilman]

@igor-dv Yeah, I use it to automatically configure things about docs. For example, react defaults to inlining story renders, whereas the rest default to iframes. React and vue support Props prop tables, the rest do not, etc.

[igor-dv]

Maybe it worth exposing "feature sets" that each framework supports instead of the framework

[shilman]

That's not a bad idea, though I plan to switch on the framework string to figure out e.g. how to extract the prop definitions. In addition, I believe that having this parameter also coincides with the multiframework stuff that @Hypnosphi is working on, so I thought it would just be a good thing to establish while I am making use of it in the docs work, rather than adding some new mechanism.