fuel-gql-client support for "https://" #266
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
…rder to support https endpoints
|
We will need this for rust sdk users hitting hosted environments behind SSL certs @digorithm |
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.
Fuel gql client accepted a string for instantiation but always parsed it as a socket addr so that it could be formatted in a way that is guaranteed to be the correct route for the fuel node. The problem with this approach is that it always assumes the client URL will be on
http. This change allows the string to be directly passed in and parsed as the URL of the fuel-core graphql endpoint, allowing users to sethttpsin the prefix if needed.