Repository navigation
fix(data): add native client examples to connect HTTP datasource page - #8633
Merged
VarshithaPamisetty merged 2 commits intoNov 3, 2026
Merged
Conversation
soberm
previously approved these changes
Oct 27, 2026
cadivus
reviewed
Oct 27, 2026
VarshithaPamisetty
force-pushed
the
fix/http-datasource-native-client-examples
branch
from
October 27, 2026 15:08
cee4a22 to
068e14d
Compare
cadivus
approved these changes
Nov 3, 2026
VarshithaPamisetty
enabled auto-merge (squash)
November 3, 2026 13:14
soberm
approved these changes
Nov 3, 2026
|
This pull request does not currently match the merge queue conditions, so it cannot be queued from here. The box comes back if it matches again. |
VarshithaPamisetty
deleted the
fix/http-datasource-native-client-examples
branch
November 3, 2026 13:24
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
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.
Description of changes:
Step 5 of the connect HTTP datasource page served TypeScript client code (
client.mutations.addPost,client.queries.getPost, in files titledApp.tsx) to all nine platforms, because the section had noInlineFilter. Added Swift, Android, and Flutter sections using raw GraphQL, and scoped the existing TypeScript example to the JS platforms.Each native section defines a type matching the
Postreturn type, then aBlockSwitcherwith the four custom operations, mirroring the structure of the parent custom business logic page. Steps 1 through 4 are unchanged: those snippets define the Gen 2 backend, which is TypeScript on every platform.Checks
yarn buildsucceeds with no errorsPosttype matches the types shownRefs #7922