Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

API V2 #1209

Closed
10 of 12 tasks
ndelangen opened this issue Jun 7, 2017 · 8 comments
Closed
10 of 12 tasks

API V2 #1209

ndelangen opened this issue Jun 7, 2017 · 8 comments

Comments

@ndelangen
Copy link
Member

ndelangen commented Jun 7, 2017

Work

TODO

  • support async components
  • adding a group | story | item at runtime should re-render hierarchy
  • support groups
  • support stateful functional components
  • create new api for getting complete hierarchy
  • create new api for getting sub hierarchy
  • create new api for subscribing to hierarchy changes
  • create new api for adding stories separating the real story from any decorators, connectors/options for addons.
  • more covfefe
  • create UI for navigating groups | stories | items
  • choose a good name for 'group' and 'item'

DONE

  • Write todo list

Choices made

-none so far-

Use cases

-I will put them in different comments for link-ability-

@ndelangen
Copy link
Member Author

Auto update UI after async story addition

// This should just update UI automatically
import('../App').then(({ default: App }) =>
  storiesOf('App', module).add('with text', () => <App />)
);

@wcastand
Copy link
Contributor

wcastand commented Jun 7, 2017

a quick tentative to resume the conversation on slack about the addon API, feel free to add more

#1212

@ndelangen ndelangen self-assigned this Jun 7, 2017
@ndelangen ndelangen added this to the v4.0.0 milestone Jun 7, 2017
@tmeasday
Copy link
Member

tmeasday commented Jun 8, 2017

@ndelangen I've looked into the auto update thing; If you want to make a separate issue I'm happy to take a crack at it.

@wcastand
Copy link
Contributor

wcastand commented Jun 8, 2017

It would be cool to handle auto load for stories. going into the .config to add every story is tedious and can be avoided i think. Maybe we can specify on the config which folder needs to be loader or by allowing to put a pattern file matching :)

Something like jest could be nice too. A "dev-watch" mode that allow you to only see the modified story to render/iterate more quickly during development.

@tmeasday
Copy link
Member

tmeasday commented Jun 8, 2017

It would be cool to handle auto load for stories

At the least I think we change the default setup to load *.story.js or the like.

@stale
Copy link

stale bot commented Oct 31, 2017

Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. We do try to do some housekeeping every once in a while so inactive issues will get closed after 90 days. Thanks!

@PhilDore11
Copy link

Any news on adding support for async components?

@blemaire
Copy link

@wcastand

It would be cool to handle auto load for stories. going into the .config to add every story is tedious and can be avoided i think. Maybe we can specify on the config which folder needs to be loader or by allowing to put a pattern file matching :)

Something like jest could be nice too. A "dev-watch" mode that allow you to only see the modified story to render/iterate more quickly during development.

Isn't this already supported using require.context ?

@shilman shilman removed this from the next milestone Apr 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants