Update README.md to explain custom file use case #1288
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
Adding documentation to indicate a use case for custom file values and options in multipart form data requests. The added sentence may have saved my team a few hours. Use case: - A user wants to upload a file to your service, and you in turn want to upload the file to an external service. - Constraint: you don't want the file to be written to disk in your service. - Because you're uploading a file from a stream, you need to add custom file-related information manually in your request to the external service.
|
Looks fine to me, thanks! |
nylen
added a commit
that referenced
this pull request
Nov 28, 2014
Update README.md to explain custom file use case
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.
Add documentation to indicate a use case for custom file values and options in multipart form data requests.
The added sentence may have saved my team a few hours.
Our specific use case: