This repository was archived by the owner on Jan 18, 2026. It is now read-only.
fix: simplify HTTP REST fallback setup#1434
Merged
alexander-fenster merged 1 commit intomainfrom Aug 23, 2023
Merged
Conversation
sofisl
approved these changes
Aug 23, 2023
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Since
google-gaxv4,fallbackis just a boolean because we removed the legacy proto-over-HTTP transport in googleapis/gax-nodejs#1471. This PR simplifies the generated code and considersfallbacka boolean (though making it still possible to pass any string, which will result in atruevalue ingoogle-gax).This is not a breaking change for the libraries customers, because the client constructor still accepts both strings and booleans; it's just the parameter processing that changes.