chai-should: improve contain transformations #501
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.
Hello,
When transforming a large test suite I noticed that the
.to.contain
transformations are not done very well when there are function calls involved.In the case when the argument for
expect()
or.to.contain()
is a function call, it would be better to simply transform.to.contain()
=>.toContain()
to avoid any problematic results, which is what my changes do.Since in Jest's
.toContain
works on strings and arrays, it should not be needed to transform.to.contain
to anything more complicated when we don't know what the result of the function call is.A real example from the codebase that I'm transforming:
...gets transformed to:
...and after these changes:
ping @skovhus