-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Add function to Parse filters + filter interface. Goal is to Parse filters and pass to `interpretTaskModes`. Attempt to parse each filter with the format `<filename>:<line_number>`, while keeping mind that some files might have `:` in their filename. Throw an error when line range is provided. Note that there is an edge case when a file has `:` and `-` in its filename. * Add `FileSpec` type In `globTestSpecs`, the filters will be matched against the files, and if there is a location in the filter, it will be included with its file, in a `FileSpec: { path, testLocations? }`. I thought it would be a good idea to include the files with the location in the same object, instead of having them in their own attribute in the config and then matching based on the path or something. But I ended up having to modify types everywhere to get this to work. I also had to modify `groupFilesByEnv` to include the `testLocations` in its output, and also modify pools to pass the test locations to `runFiles`. - Move the filter parsing inside `globTestSpecs` and revert related type changes * Report disabled `includeTaskLocation` Add and handle new error `IncludeTasklocationDisabledError` * Report file not found if a test location was specified - The reason for this is that we're using a more strict matching that requires full path to be specified * Report wrong line number - Got rid of the confusing warning. Current behavior is that if user specifies a file with and without line numbers, it will not have an effect (e.g. `test.ts:3 test.ts` will match on line 3 only, not all files).
- Loading branch information
Showing
20 changed files
with
275 additions
and
79 deletions.
There are no files selected for viewing
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
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
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
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
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
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
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
Oops, something went wrong.