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

Login __generated__ file with mutation defined in lowercase is causing errors

Open
#179 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
55/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Stale
Tech stack
graphql, javascript, typescript
Domain
documentation

Research direction

Review the mutation section linked in the issue, the generated pages/generated/login.ts file, and server/src/tests/integration.js. Check that the mutation naming and generated type references use the same casing throughout; the tutorial code and integration test should be consistent and no longer produce the reported errors.

Written by the indexing model from the issue text.

Description

Following the official documentation and the rest of the tutorial, queries and mutations are defined with the first letter in uppercase (PascalCase). However, in this part of the tutorial the mutation Login is defined lowercase (I see that in the final version of the tutorial this is corrected):

export const LOGIN_USER = gql`
  mutation login($email: String!) {
    login(email: $email)
  }
`;

The corresponding generated file (pages/__generated__/login.ts), Login type appears as well in lowercase but the related code is assuming they are in uppercase, throwing errors:

const [login, { loading, error }] = useMutation<
  LoginTypes.Login,
  LoginTypes.LoginVariables
>(LOGIN_USER);

The mutation Login in the integration tests (server/src/__tests__/integration.js) is also defined in lowercase:

const LOGIN = gql`
  mutation login($email: String!) {
    login(email: $email)
  }
`;
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.