Current Behavior
Added tsdx to a project where test files are in the same dirs as the files under test like this:
src/
dir1/
file1.ts
file1.test.ts
... and ran npm run lint. This is the error generated:
Error: No files matching 'test' were found.
The linter doesn't finish running because of it.
Desired Behavior
Linter doesn't error out due to this project structure.
Suggested Solution
Since this is a common project configuration to ensure you have a test suite per file, either edit the default configuration to support this setup or add a flag to tsdx create or tsdx lint that supports it.
Who does this impact? Who is this for?
All users, potentially. Specifically, people who have their test files next to their files under test in their dir structure.
Describe alternatives you've considered
- A tsdx eject command that lets you override these settings (sort of against the spirit of the project, though)
- Stopping writing tests with this style (but the benefits outweigh the costs)
Additional context
Current Behavior
Added tsdx to a project where test files are in the same dirs as the files under test like this:
... and ran
npm run lint. This is the error generated:Error: No files matching 'test' were found.The linter doesn't finish running because of it.
Desired Behavior
Linter doesn't error out due to this project structure.
Suggested Solution
Since this is a common project configuration to ensure you have a test suite per file, either edit the default configuration to support this setup or add a flag to
tsdx createortsdx lintthat supports it.Who does this impact? Who is this for?
All users, potentially. Specifically, people who have their test files next to their files under test in their dir structure.
Describe alternatives you've considered
Additional context