GraphQLClient.tar.gz

REACT_APP_GITHUB_PERSONAL_ACCESS_TOKEN

GITHUB_PERSONAL_ACCESS_TOKEN

RunApp

RunApolllo

RunGraphQLReact

This course was written to be as practical as possible. It offers an interactive learning experience, starting off with a general introduction to GraphQL and proceeding to allow you to play with GraphQL Queries and Mutations using GitHub’s GraphQL API.

After getting you comfortable with the basics of GraphQL, the course moves on to how to use GraphQL with React and then on how to integrate it with Apollo Client. You'll implement an issue tracker application using GraphQL combined with both React and Apollo Client.

Finally, with this course Educative introduces its newest feature: A live VM. You will now have access to a terminal with a native look and feel where you can modify code and see changes in real time - all inside your browser!

A Practical Guide to GraphQL: From the Client Perspective

Having a clearer separation between data-layer and view layer.

Having no access to the local state of the component where the Render Prop is used.

Keeping your data-layer concise by inserting the data-layer into the view-layer instead of co-locating both layers.

Having a more intuitive way of using props from the component in the Query and Mutation components.

When should you use a Render Prop over a Higher-Order Component?

When should you use a Render Prop over a Higher-Order Component?

Having access to the local state of the component where the HOC is used a enhancement.

Keeping your data-layer concise by co-locating both layers instead of inserting the data-layer into the view-layer.

Having a more intuitive way of using props from the component in the Higher-Order Component.

When should you use a Higher-Order Component over a Render Prop?

When should you use a Higher-Order Component over a Render Prop?

Splitting up the component in smaller components that are focused on only a few queries/mutations.

Using Lower-Order Components over Render Props when it would make sense.

Having no threshold of allowed nested Query/Mutation components.

Use the Apollo Client instance directly and default to imperative query and mutation calls.

What’s the best strategy when using render props to avoid deep Query/Mutation component nesting?

What’s the best strategy when using render props to avoid deep Query/Mutation component nesting?

An Introduction to GraphQL

How to Get Started

Exploring GitHub's GraphQL API

Combining React with GraphQL

Introducing Apollo Client with GraphQL

React with Apollo and GraphQL

Local Installation Guide

Quiz on GraphQL Mutation with Higher-Order Components