Updating httpposion and adding end_point configuration #30
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 an end_point to the config.exs so that it is configurable for the US markets
Adding an end_point to the config.exs so that it is configurable for the US markets
# Conflicts: # README.md
|
Whoops I must have missed the notification. Thanks for the pull request! |
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.
Updating the httpposion because of this issue hackney 591
Adding a
end_pointconfiguration attribute toconfig.exsfor the api end_point to allow for configurations pointing to the US binance API endpoint. The default remains the same. There should be no impact or changes required for existing applications pointing to the default API.