http: add CheckRedirect field to Client for compatibility with oauth2 #41
Conversation
This file contains hidden or 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
This change introduces a CheckRedirect field to the http.Client struct in TinyGo, mirroring the behavior of Go's standard library http.Client. The purpose of this addition is to resolve build errors in projects that rely on packages (such as golang.org/x/oauth2) expecting the Client to have a CheckRedirect field. The field provides no functional change within TinyGo’s HTTP client at this time — it is only included for API compatibility and compilation success. There is no effect on runtime behavior unless explicitly used by downstream code.
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.
This change introduces a CheckRedirect field to the http.Client struct in TinyGo, mirroring the behavior of Go's standard library http.Client.
The purpose of this addition is to resolve build errors in projects that rely on packages (such as golang.org/x/oauth2) expecting the Client to have a CheckRedirect field. The field provides no functional change within TinyGo’s HTTP client at this time — it is only included for API compatibility and compilation success. There is no effect on runtime behavior unless explicitly used by downstream code.