Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Some improvement suggestions for newbie reading the client tutorials (section 5 to 8)

Open
#71 2 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
graphql, react, typescript
Domain
documentation

Research direction

Review the linked client tutorial sections for React Apollo, fragments, authentication, local queries, virtual fields, and direct writes. Check each listed missing import, component, constant, resolver, typeDefs, or source-file reference against the tutorial context; done means every referenced item is introduced or its location is explained.

Written by the indexing model from the issue text.

Description

https://www.apollographql.com/docs/tutorial/client.html#react-apollo

  • no react and react-dom imports
  • where did Pages component came from?

https://www.apollographql.com/docs/tutorial/queries.html#fragments

  • LAUNCH_TILE_DATA should be above GET_LAUNCHES
  • please mention src/pages/launch.js

https://www.apollographql.com/docs/tutorial/mutations.html#authenticate

  • where did resolver and typeDefs came from?

https://www.apollographql.com/docs/tutorial/local-state.html#local-query

  • where did injectStyles() came from?

https://www.apollographql.com/docs/tutorial/local-state.html#virtual-fields

  • where did GET_CART_ITEMS came from?

https://www.apollographql.com/docs/tutorial/local-state.html#direct-writes

  • where did StyledButton component came from?
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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apollographql/fullstack-tutorial

All issues in apollographql/fullstack-tutorial

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.