docs(graphql): use empty proxy targets - #153
Merged
Merged
Conversation
josegironn
requested review from
jasonzbao and
rishikesh-major
as code owners
September 5, 2026 01:44
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Use an empty proxy target to call the configured GraphQL endpoint without adding a slash. Show
proxyFetch("")directly and useuri: () => ""with Apollo, whose plain empty-string URI falls back to/graphql.Depends on the companion mono-builder empty-target fix being deployed before this guidance is released.
Validation: checked Apollo's upstream
selectURIimplementation andgit diff --check. The skill validator could not run because local Python lacks PyYAML; frontmatter is unchanged.