refactor(tests): add path to module mapper for jest tests #532
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.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
With NestCLI we can now use the path option of tsconfig to add path resolution, and have it included in the generated build.
Unfortunately this does not work with jest.
What is the current behavior?
When we add a new path to tsconfig, and use this new path in imports, jest can't resolve the modules.
What is the new behavior?
Jest can now resolve modules imported using the path config from tsconfig file
Does this PR introduce a breaking change?
Other information