update sanitizeSpecsPattern logic #788
Merged
Conversation
This file contains hidden or 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
sparsh00
previously approved these changes
Mar 6, 2024
hari-haran-ss
previously approved these changes
Apr 15, 2024
hari-haran-ss
previously approved these changes
Apr 18, 2024
hari-haran-ss
approved these changes
Apr 18, 2024
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Currently, we wrap the specPattern with {} if we find comma-separated values. This is required but it breaks a case where the pattern is of this type -
"integration/{folderA,folderB}/*.spec.ts".With this PR, we are handling the above-mentioned edge case and will only wrap the specPattern with {} if we find comma-separated values.