Fix expect finder utility #26
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
it looks like the mocha plugin is causing some issues on CI. could you remove that dependency change and limit the PR to just include the expect detection changes? |
|
@Turbo87 Fixed! Sorry, not sure why I ended up with those deps... this code started in a debugging place for sure. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Attempting to build one of my own custom rules on top of this repo, I found some cases in which the
findExpectCallfunction was not accurately finding all expect statements. Particularly ones which had function calls within their assertion chain.The first commit demonstrates the issue, the second commit solves it.