Closures passed to the skip
method are now bound to the test case
#338
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.
Hey y'all,
something that came up in the stream yesterday was this:
Obviously, this condition requires the test case setup method to already have been run, so you wouldn't be able to write it in Pest's
skip
method. This PR enables this functionality by moving the conditional logic into the HigherOrderMessage itself, and binding the conditional closure to the test case.This feature actually opens up the potential for other bound callable too, because now when adding to a HigherOrderMessage, you can simply use the newly built
when
method and pass a conditional; it will always be bound to the test case.Kind Regards,
Luke