Issue 1059: tsJestConfig overriding jest.config.ts global ts-jest config #1896
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.
fix(testing): merge rather than replace
ts-jest
property on global configresolves #1059
Please make sure you have read the submission guidelines before posting an PR
Current Behavior (This is the behavior we have today, before the PR is merged)
Any globals specified in jest.config.js are overridden due to reassignment of the
ts-jest
property of the globals object. This is a brute force reassignment, rather than a merging of globals defined in jest.config.js and those brought in via angular.json config.Expected Behavior (This is the new behavior we can expect after the PR is merged)
Globals in jest.config.js will be properly merged with config brought in via angular.json. Critically, this will allow
diagnostics
to be set to false, which seems to be the primary use case that people are running into issues with.Issue
1059