Using fragment in `launches.js` stops data from being loaded.
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 38/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- graphql, javascript, react
Research direction
Start in launches.js by comparing the working inline query with the fragment-based GET_LAUNCHES query, then reproduce the missing request against the GraphQL server. Done means the fragment-based query sends a POST request and the launch data is loaded into the component.
Written by the indexing model from the issue text.
Description
Are you sure that presented fragment is correct? I mean it looks right but when changing from
const GET_LAUNCHES = gql`
query launchList($after: String) {
launches(after: $after) {
cursor
hasMore
launches {
id
isBooked
rocket {
id
name
}
mission {
name
missionPatch
}
}
}
}
`;
to solution with fragments:
export const LAUNCH_TILE_DATA = gql`
fragment LaunchTile on Launch {
__typename
id
isBooked
rocket {
id
name
}
mission {
name
missionPatch
}
}
`;
const GET_LAUNCHES = gql`
query GetLaunchList($after: String) {
launches(after: $after) {
cursor
hasMore
launches {
...LaunchTile
}
}
}
${LAUNCH_TILE_DATA}
`;
Data is never properly loaded into the component:
When using the fragments I can't see any POST request performed against my graphql server.
- Dominant language
- TypeScript
- Stars
- 1.2k
- Forks
- 808
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from apollographql/fullstack-tutorial
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
investigate
Difficulty 4/5 3-5 days Newbie friendliness 30/100
-
documentation
apollographql/fullstack-tutorial#285 · 3 comments · 1 assignee ·
-
investigate
Difficulty 3/5 1-2 days Newbie friendliness 35/100
apollographql/fullstack-tutorial#255 · 2 reactions ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 25/100
apollographql/fullstack-tutorial#254 · 2 comments ·
All issues in apollographql/fullstack-tutorial
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
bug v2
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
modelcontextprotocol/inspector#2458 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
railmapgen/rmp-gallery#4068 ·
-
Mend: dependency security vulnerability status: needs triage 🕵️♀️
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
carbon-design-system/ibm-products#9907 ·