build: move jest-circus/ facade to jest/ #3400
Merged
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.
Description
In this PR, since there is only single integration with
jest
andjest-circus
, and the latter is a default choice for Jest 27, and the only choice for Jest 28 (unlessjest-jasmine2
is installed and configured explicitly), I consider it justified to shorten the paths to the user-facing files.Required changes from the users
In the environment class file:
In Jest config:
Migration flow
As for the attempts to import the files at their old locations, the users will be seeing warnings:
That should enact the migration process smoothly enough.