(docs): add Jest and ESLint subsections to Customization #697
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.
while the docs do say these are run fairly directly, recently folks
seem to be particularly confused about how to configure Jest
jest.config.js
and.eslintrc.js
to makethat a bit more clear
package.json
options as I think that should beimplicitly implied enough now
cases (see existing issue)
tsdx test
flags are forwarded toJest
also add links to "its own config" for each of the Babel, Jest, and
ESLint subsections so people can look at the source quickly if they
want
and specify the merge behavior for each, i.e. shallow or deep
To help with issues like #695 and #692 (comment) as I guess it's not clear enough that you can do this already
Also specifies merge behavior of Babel since #543 is a thing