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

CLI option to specify Storybook configuration #29

Closed
kevinwolfcr opened this issue Apr 3, 2016 · 4 comments
Closed

CLI option to specify Storybook configuration #29

kevinwolfcr opened this issue Apr 3, 2016 · 4 comments

Comments

@kevinwolfcr
Copy link

Hello!

I've started using react-storybook on a component library I am authoring and so far I like it. The only thing I haven't found on the docs and I think it can be better is the ability to specify the config.js path.

Maybe an option like --config on the cli?

@arunoda
Copy link
Member

arunoda commented Apr 3, 2016

Okay. That's a good idea. May be it's the config dir.

@fionawhim
Copy link

I'd second this. The config file is an important part of the overall codebase and it's hidden inside a dot-directory.

@kevinwolfcr
Copy link
Author

@arunoda I think it would be better to specify filepath rather than directory. On that way I can name the file whoever I want.

@arunoda
Copy link
Member

arunoda commented Apr 5, 2016

@Kevin-Wolf We will have a few config files over the time. (Currently we've two)
So, it's better to have a directory.

ndelangen pushed a commit that referenced this issue Apr 5, 2017
ndelangen pushed a commit that referenced this issue Apr 11, 2017
ndelangen pushed a commit that referenced this issue Apr 11, 2017
Write a storybook for components in this addon #25
ndelangen pushed a commit that referenced this issue Apr 11, 2017
ndelangen added a commit that referenced this issue Apr 11, 2017
ndelangen pushed a commit that referenced this issue Apr 23, 2017
Fix resize with scrollbar
thani-sh pushed a commit that referenced this issue May 24, 2017
Give Travis permission to deploy
JReinhold added a commit that referenced this issue May 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants