Make Pendable resolvable after being called. #15
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
…resolved with their fallback.
Add inline documentation for DynamicPendable
Address swiftlint concerns
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.
Resolves #2
Pendablebeing static works, but is rather clunky.This provides a safe way to allow you to resolve Pendable calls after they're made, instead of before.
Pendablenow requires you to initialize it with a fallback (which isn't different from how it was before). This fallback is used when you re-stub a spy (it resolves any outstanding calls with the fallback value), or when some amount of time has passed after calling the spy.A future PR will be written documentation describing exactly how to use Pendable.