chai-should: don't update member expressions inside expect calls #503
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 again,
I noticed that the
chai-should
codemod did fail to properly transformexpect(fetchMock.called("/url"))
. (docs: http://www.wheresrhys.co.uk/fetch-mock/)I thought that a good fix would be not to update the matchers if they appear inside an
expect
call. This did not break any of the new or existing test cases.I'm not sure if there is a better way than what I used in the
isInsideExpectCall
function that I added.input:
expected result:
actual result before the fix:
ping @skovhus