Code from the GraphQL Bootcamp by Andrew Mead on Udemy

Completed Section 9 - Testing

These are query and mutation examples to remember the syntax when it's more than just a simple query or mutation.

If you name your queries, mutations and subscriptions, then you can have multiple ones in each tab and pressing the go button will show a list of actions to run. e.g.

query Users {
  users {
    id
    name
    email
    age
    posts { title }
    comments { text }
  }
}

mutation NewPost {
  createPost(
    data: {
      title: "A new hope"
      body: "Battle among the stars"
      published: true
      author: "10"
    }
  ) {
    id
    title
    body
    author { name }
  }
}

mutation DeleteUser {
  deleteUser(id: "10") {
    id
    name
  }
}

mutation updateUser {
  deleteUser(id: "10", data: { email: 'newjulian@example.com }) {
    id
    name
    email
  }
}

{
  first: company(id: "1") {   /* named result */
    ...companyDetails
  }

  company(id: "2") {
    ...companyDetails
  }
}

mutation {
  addCompany(name: "Woolworth") {
    ...companyDetails
  }
}

fragment companyDetails on Company {
  id, name, description
}

query Song($id: ID!) {
  song(id: $id) {
    id, title
  }
}

mutation AddSong($title: String!) {
  addSong(title: $title) {
    id
  }
}

• Obviously, I am using git from the very beginning 😀

• I have installed ESLint in each project. My preferences are semicolons and single-quotes YMMV 😀

• I have kept the basics files, startable with npm run start-basics.

• I use arrow functions almost exclusively.

• I destructure much more and don't declare redundant arguments, so this:

Post: {
  author: (parent, args, context, info) => USERS.find((user) => parent.author === user.id),
},

becomes this

Post: {
  author: ({ author }) => USERS.find(({ id }) => author === id),
},

at least in the early stages.

• I have implemented many of the suggested tests, and some of mine are subtly different, e.g. my comment and post subscriptions do an update rather than a delete, so that the ID can be checked as part of the subscription callback.

I have used Git at the command-line for more than 10 years. Over that time, I have tried many different graphical shells for Git, without finding one that was easier and nicer to use than the command-line (in my view).

I have now found that GitKraken is an excellent Git shell and would advise using it to everyone.

If you have any questions about this repository, or any others of mine, please don't hesitate to contact me.