You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Provide a method for stylized title generation, such as automatically generating a title based on file path or a template based approach with a set of known macros.
Why
Currently there are two options: fully static or fully dynamic titles. Fully dynamic titles (e.g. #10959) is a flexible way for users to configure Storybook's navigation sidebar in CSF based on things like file paths of the story files. Unfortunately, fully dynamic titles are difficult for tools to statically analyze, leading to limitations in the tooling.
What
Some options, TBD:
Automatic title generation by default based on the path to the file (which can be manually overridden using a static title)
A set of known macros (similar to __dirname)
The text was updated successfully, but these errors were encountered:
Thanks for creating this, @shilman - we came across this issue while trying out Storybook 6, and it took us a while to dig down to the root cause of #9582
Happy to see #10959 address that in at least some way, but I think we'd also be very happy with a standardized, filesystem-based approach to allow easy static analysis to continue, given that we're probably going to try to use static names for now, and see how unwieldy it feels (~30 components at the moment). Let us know if there's anything we can give feedback on or help with
Provide a method for stylized title generation, such as automatically generating a title based on file path or a template based approach with a set of known macros.
Why
Currently there are two options: fully static or fully dynamic titles. Fully dynamic titles (e.g. #10959) is a flexible way for users to configure Storybook's navigation sidebar in CSF based on things like file paths of the story files. Unfortunately, fully dynamic titles are difficult for tools to statically analyze, leading to limitations in the tooling.
What
Some options, TBD:
__dirname
)The text was updated successfully, but these errors were encountered: