Unable to select story with --only
See original GitHub issueI’m trying to run chromatic only for a single component, but cannot get the argument to --only
to work.
When run with --list
I get e.g.:
→ Single Case / Top Bar:Main Case Data
→ Single Case / Top Bar:Minimal Data
So I tried running with --only "Single Case / Top Bar:*"
. This causes an error:
✖ Invalid --only Value must be provided in the form ‘Path/To/MyStory’. Globbing is supported, for example: ‘Pages/**’
Leaving away the spaces around the slash gets around the error, but selects no stories. Maybe the regex for the argument needs to allow spaces?
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
[Updated] Instagram 'Add Yours' Chain Story sticker not ...
Some Instagram users are reporting that the new 'Add Yours' Chain Story is sticker not working for them.
Read more >Can't see Story option while creating an issue
My Jira account is not giving me the option to Create a story. The only options in the drop down are Epic or...
Read more >Instagram Stories Not Loading? A Troubleshooting Guide
The first thing you should do if your Instagram Stories are not loading is to check your internet connection. If you're on a...
Read more >Top 9 Fixes for Instagram Story Highlights Not Loading Issue
Step 1: Launch the Instagram app and go to your profile screen. Tap on the three-bar icon at the top. Select Settings. ;...
Read more >Can't Share Post to Instagram Story – Why Not? - Alphr
This feature is only available for public profiles. ... Select Story, then toggle the Allow sharing to story option.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Ok this seems to work indeed. Not sure how it could have been clear to me 🤔 Maybe change the format in
--list
?When I’m trying to fix a problem for a big component, we usually have a lot of stories for it, meaning that
--only-changed
will result in for example 20-40 snapshots being taken, compared to only 1 if I’m testing my changes via--only
. In some cases I need to do this, because some of the problems we encounter only occur in snapshots and not in storybook itself.Like for example, I have a component that uses DeckGL + ReactMapGL + Mapbox, and the map loads perfectly fine in the chrome snapshot, but doesn’t load at all in the firefox snapshot. It’s just blank for some reason, even though in storybook we have no issues at all on firefox.
I still have no idea what’s causing that, so while I’m testing things like that, I’d very much prefer to save on snapshots by only running a specific story and not everything related to that component.