3. Using APIs

The GitHub GraphQL API is very well documented, and even though the focus of this tutorial isn’t learning and using GraphQL, it’s a great opportunity to fetch Carbon-related data for this Carbon tutorial.

To do so, we’ll be using Apollo Client, the front-end component of the Apollo Platform. Apollo provides several open source tools for using GraphQL throughout your application’s stack. Apollo Client is a sophisticated GraphQL client that manages data and state in an application.

A preview of what you will build (see repositories page):

This tutorial has an accompanying GitHub repository called carbon-tutorial that we’ll use as a starting point for each step. If you haven’t forked and cloned that repository yet, and haven’t added the upstream remote, go ahead and do so by following the step 1 instructions.

With your repository all set up, let’s check out the branch for this tutorial step’s starting point.

Install the app’s dependencies:

Then, start the app:

You should see something similar to where the previous step left off. Stop your app with CTRL-C and let’s get everything installed.

We’ll need to install three new dependencies to incorporate Apollo into our application.

Install them with the command:

You’ll need a personal access token from your GitHub account in order to make requests to the GitHub API. Check out this guide to see how to get one.

When you get to the scope/permissions step, you can leave them all unchecked. We don’t need any special permissions, we just need access to the public API.

Once you have your token, we need to put it in a place where create-react-app can use it. When your application is being built and developed, create-react-app will parse environmental variables in any file that starts with .env and make them available under process.env.MY_VARIABLE.

One caveat is that we need to start our variables with REACT_APP_. You can read more about environmental variables in create-react-app’s guide.

Since we don’t want to commit this file to Git, we can put it in .env.local which is in our .gitignore list. Your file should just have a single line like this one, where the xs are replaced with your unique token.

Go ahead and start your app with yarn start, or, if your app is running, you’ll need to restart it to get access to this token.

The @apollo/client library gives us the components that we need to put at the base of our application. Typically the best place for things that need to wrap the entire application is at the root of the application. For us, that’s at src/index.js.

Add these imports to src/index.js:

Next, define the cache and make your client by providing a URI for the GitHub GraphQL API as well as an authorization header using the environmental variable you just added to .env.local.

Now we can wrap our application with ApolloProvider. At the same time, we’ll pass in the client we just made as a prop to the ApolloProvider component. Replace:

With:

Add the following imports below the react import in RepoPage.js:

Next we’ll assemble our GraphQL query to fetch only the data we need from the GraphQL API. We’ll do this using the gql helper we just imported. The gql helper lets you write GraphQL queries using interpolated strings (backticks) in JavaScript. In addition, we’ll be using the useQuery component from @apollo/client which gives us some great information about our query’s loading state in addition to the data.

You can use GitHub’s explorer tool to write and test your own queries. Try copying the query below and experiment with changing the properties. You can also click the “Docs” button in the top right of the explorer to view all of the available data and query parameters.

If you’d like some more information regarding writing queries and using the Query component, we recommend Apollo’s documentation on this topic.

Add this after your imports:

Below that, we should have our table headers set in a previous step that are good to go. Let’s also keep our example rows below that.

Our last column in the data table will be a comma-separated list of repository and home page links, so let’s create a component called LinkList.

Import Link at the top of RepoPage.js. The imports should look like this.

Then use Link in this component that has two props (url and homepageUrl) and returns an unordered list. If the repository does not have a home page URL, only render the repository link.

As a final helper, let’s create a function that transforms row data to our expected header keys. Notice how we’re using our new LinkList component to generate the value of the links key in each row.

At this point, we should run our query and console.log() the results to verify that the request is working.

The useQuery component from @apollo/client lets us render different content based on the state of our request. When loading is true, we’ll render Loading... for the time being. If there’s an issue, we’ll render the corresponding error message using error.

Finally, if neither of those are true, it means we have our data! One nice advantage of GraphQL is that as long as there are no errors, we can be certain the properties on the data we requested aren’t null.

We need to define the loading, error, and data using useQuery. We will update the beginning of the RepoPage component with the following.

Notice how we’re passing the REPO_QUERY that we previously defined into the useQuery hook.

The page will look the same as we’re still rendering our static example rows, but if you view your browser’s console (e.g. Chrome DevTools), you should see the response from GitHub!

Now that we have that data, let’s populate the data table. Replace console.log(data.organization); inside if (data) with the following that destructures the data.organization object. Once we have the repositories, we can call our getRowItems() helper to build the data table rows.

Here will will also add our grid we previously made. The data should now look like this:

Then, towards the top of RepoPage.js delete the rows array because we no longer need the example rows.

The data table component and its pieces use a common React pattern called render props. This is a really powerful way for libraries to give developers control of rendering and manipulating their data.

Revisiting RepoTable.js, we are already passing in our row objects along with headers for each column. The render prop is being used to tell the data table how to render the headers and rows. That prop takes a function that receives the processed headers and rows as arguments as well as some helper functions for rendering the table.

One common hurdle with the data table is how to access data that might not correspond with a table column but is needed to compute the value of a cell that does. The data table component processes and controls only the row properties which corresponds to headers (columns). Because of this, the rows object you get access to in the render prop function is different than the one you passed in to the rows prop.

We need to modify one aspect of the data table because if you expand a row, it says Row description. We want to update that with the repository description coming from the GitHub API. This is an example of where we need a simple look-up function to find the data we care about - data that does not directly correspond to a column.

To do so, in RepoTable.js, add this look-up function as the first lines inside the RepoTable. This should go immediately before the component’s return().

Finally, in RepoTable.js, replace <p>Row description</p> with:

At this point, the first time that you visit the repositories page, we’re querying the GitHub API and rendering the response through the DataTable component. We could stop here, but there’s more to be done! Let’s replace the Loading... string with the DataTableSkeleton component.

To do so, back to RepoPage.js, add the DataTableSkeleton import by modifying the existing carbon-components-react import.

Then replace the if (loading) return 'Loading...'; with:

We need to tell the loading skeleton how many rows to render, so let’s use 10 skeleton rows to prepare for the next enhancement…

Pagination! Instead of rendering every repository, let’s add pagination to the data table to only render 10 at a time. Depending on your specific requirements, you may need to fetch new data each time that you interact with the pagination component, but for simplicity, we’re going to make one request to fetch all data, and then paginate the in-memory row data.

We’ll be using React Hooks to manage our state.

Import React’s useState by modifying the React import.

Then initialize the new state variables that we’ll use for pagination as the first lines inside the RepoPage.

This initializes the total number of rows and the index of the first row to 0, and the page size to 10 as we also specified in our loading skeleton.

Then we need to update our RepoTable rows prop to only render the subset of rows for the current “page”. Update <RepoTable headers={headers} rows={rows} /> to:

Finally, let’s add the Pagination to update our state variables and cause the data table to render new rows.

Import Pagination by updating the @carbon/react import.

Immediately after the RepoTable closing tag (/>), add the Pagination component using the state variables that we previously initialized.

That does it! Your data table should fetch GitHub data on first render. You can expand each row to see the repository’s description. You can modify the pagination items per page and cycle through pages or jump to a specific page of repositories.

We’re going to submit a pull request to verify completion of this tutorial step.

Run the CI check to make sure we’re all set to submit a pull request.

Before we can create a pull request, format your code, then stage and commit all of your changes:

Then, push to your repository:

Finally, visit carbon-tutorial to “Compare & pull request”. In doing so, make sure that you are comparing to react-step-3 into base: react-step-3.