doc: Explain behaviour of when/expect #153
Open
Conversation
This file contains hidden or 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
I found the behaviour of when/expect confusing, and couldn't see how to set the "always" behaviour. This patch adds a bit more clarity to that area of usage to the readme.
This took me hours to figure out.
|
Apologies for the delayed reply on this, but isn't this effectively duplicating the "Match Behavior" section of the readme? |
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.
I found the behaviour of when/expect confusing, and couldn't see how to set the "always" behaviour. This patch adds a bit more clarity to that area of usage to the readme.
Hopefully I've the updated description of the behaviour is accurate, I've not used this library much.
Thanks for the library, solves a painful problem.