Document transport options #80
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
|
Ok, saw you merged #78, will update this with timeout in a bit |
whatyouhide
requested changes
Feb 15, 2019
ericmj
approved these changes
Feb 15, 2019
Co-Authored-By: voltone <bram.verburg@voltone.net>
|
Thank you! 💜 |
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.
See #79
If this is too much to document inline in
Mint.HTTP.connect/3,4then perhaps we can define a custom type for:transport_optsand move the new section to a typedoc. I imagine documenting them underMint.Core.Transport.{TCP, SSL}instead is not desirable.