-
-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
[Feature] Improved SearchBox for stories #4139
Comments
Interesting Idea 👍 |
@christopherstat Let's have a chat on our slack? |
Wow, I was literally just explaining to my team how cool this functionality would be to find that a few days ago it had been raised here! I found myself scrolling through the list of my components trying to find form related components. It would be really nice if you could tag components and then filter by those tags, e.g... ['form', 'input']. |
In my branch the search is expanded to full text on every property of the story. I'd like to implement fuzzy search on it, would you care to help with that @nicholasmaddren or @christopherstat ? |
WIP: #4086 |
The features @ndelangen described are merged in the v5 branch. |
Hello everyone! First time poster here.
Currently search is performed exclusively on the name of the story, but it might be relatively easy/safe to take advantage of Story Parameters to make search a bit smarter.
I wanted to implement an interactive Design System in storybook in which stories could be "tagged" and searched for by typing in such tags, and enable using the same Markdown files used to document a story so that matching terms within them would be found and consequently the story "matched" in the search results. (inspired by Storybook Readme).
I was thinking it could be a matter of providing the attributes directly in the story, such as:
I'm not sure of what this all involves, but I presume it would mean:
<SearchBox />
to receive additional data from the stories (possibly here).api.add(title, story, params)
so that you can provide said tags and/or markdown files.What do you guys think? I'd be happy to help with the implementation and feedback!
The text was updated successfully, but these errors were encountered: