escape special characters in onlyStoryFiles filenames #942
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![codacy-production[bot]](https://avatars.githubusercontent.com/in/56611?s=60&v=4){kind=small}
JonathanKolnik
added
release
JonathanKolnik
deleted the
jono/ap-4310-chromatic-is-not-capturing-all-affected-stories-when
branch
|
🚀 PR was released in |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
onlyStoryFiles filenames that contain special characters are potentially treated as globs during the picomatch evaluation step of TurboSnap
e.g.
./example-(new).stories.js=>./example-\\(new\\).stories.jsThis PR escapes those special characters so they are treated as the true filepath and not a glob.
📦 Published PR as canary version:
11.0.6--canary.942.8193875287.0✨ Test out this PR locally via:
npm install chromatic@11.0.6--canary.942.8193875287.0 # or yarn add chromatic@11.0.6--canary.942.8193875287.0