This repository has been archived by the owner on Apr 30, 2024. It is now read-only.
encode / decode _process_results option #170
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
|
+1 |
1 similar comment
|
+1 |
|
@beaulyddon-wf for merge |
|
+1 |
beaulyddon-wf
added a commit
that referenced
this pull request
Oct 8, 2015
encode / decode _process_results option
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
currently, the _process_results option is not correctly encoded/decoded with the rest of the async options. passing in a callable will result in a json error. this change handles _process_results exactly like _context_checker is currently handled.
@beaulyddon-wf @tannermiller-wf