refactor: expose legacy extend-expect #189
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.
What:
This PR is exposing alternative
legacy_toXxx
matcher naming, in order to support ongoing migration of Jest Native matchers to RNTL, so that users can use both new RNTL matchers and legacy Jest Native matchers to gradually migrate their code.This PR is not doing advertising this change yet, as the RNTL migration is ongoing. I would add relevant documentation when RNTL matchers are read.
Why:
This is needed as migrated matchers are usually named the same as Jest Native matchers, so without this there would be a naming clash.
How:
Add
legacy-extend-expect
export, so which extendsexpect
withlegacy_toXxx
matchers rather than typicallytoXxx
naming. The originalextend-expect
remains still available, so existing users should not be affected.Checklist: