React Props Refine

Clean up the React Props GitHub API Program.

Key Features

The main goal will be to query the GitHub API for a view of your account. We are building on work we did before.

Create React Refine View

This version of the app displays a few rows from the data returned from GitHub API in a component called GetUserInfo. Recall that this is a REST API, so we can call it by simply typing a URL into the address bar of browser. To see this in action, click the link below:

In your program remember to query your account not mine.

  • Display at least five rows from the users URL as shown above. Don’t display them all, as we will find a shortcut to help you create big forms with lots of fields.
  • Make sure all your tests pass for the GetUrlPage component, the GetFoo component, the SmallNumbers component and the ElfHeader component. Each component’s tests should be in its own file and all tests should be in a directory called src/__tests__.
  • For now, continue to display the other information, such as SmallNumbers and GetFoo. Ultimately, we will learn how to use client side routes to switch component views, but for now, just show all the data on the same page, as shown below.
  • Strive to eliminate all errors and warnings in your tests, in Chrome Developer Tools, and at the command line for your server and client.

Don’t fuss too much at this stage with making things beautiful. Right now, we are just trying to get to the point where we can create components and tests. Appearance and site navigation come later. Soon, but later.

Create React Refine Altogether


Change the name of the folder in which the program is stored to GitExplorer. Perhaps something like:

git mv week02-rest-basics/ GitExplorer

Create CSS and Image Directories

Inside the src directory create directories called css and images. Move your CSS and SVG files into these directories. Check your tests and run your program and make sure you are not getting errors or warnings.

  • Start your program: npm/yarn start
  • In Chrome, open the Developer Tools: F12 or CTRL-SHIFT-I or **Settings More Tools Dev Tools**

Check for Warnings and Errors

Check for warnings or errors

Uh-oh! A warning

IMAGE: Uh-oh! To fix this, I would follow the hints in the warning to my src/index.js file.

Same warning from command line

IMAGE: The same warning as seen from the command line. Sometimes you might see problems at the command line that you don’t see in the developer tools and vice versa. As you result, you should check both places.

When you turn in your code, you should always ensure that your program is completely free of warnings and errors.

Add Display for API User

By this time you should have refactored your code so that there is nothing about headers, SmallNumbers, or retrieving information from /api/foo in App.js. We want to re-purpose App.js so that it can be used to handler our request for /api/users.

Add request to your server:

npm install request –save

Require it at the top of routes/api.js

var request = require('request');

The data I return from the server is shaped, for now, like this:

router.get('/user', function(req, res, next) {
    var options = {
        url: '',
        headers: {
            'User-Agent': 'request'

    request(options, function(error, response, body) {
        // Print the error if one occurred
        console.log('error:', error);
        // Print the response status code if a response was received
        console.log('statusCode:', response && response.statusCode);
        // Print the HTML for the Google homepage.
        console.log('body:', body);
        res.send({error: error, response: response, body: body});


Note that I’m sending back three properties:

  • error
  • response
  • body

The last contains the core data that we want to retrieve from GitHub. The first few lines should look something like this, with your data rather than mine:

    "login": "charliecalvert",
    "id": 1811478,
    "avatar_url": "",
    "gravatar_id": "",
    "url": "",
    "html_url": "",
    "followers_url": "",


You will also want to set up CSS to control the Avatar URL:

img.avatar {
    width: 75px;
    height: 75px;

Display User Data

The first step would be to rename components/App.js to components/GetUserInfo.js. That might look something like this on your system, where you may need to change or skip the first line:

$ cd GitExplorer/client/src/
$ git mv components/App.js components/GetUserInfo.js

Open up the source for GetUserInfo.js, and rename the component class from App to GetUserInfo. This will take two changes:

class GetUserInfo extends Component {

export default GetUserInfo;

Create a getUser method that looks a little like this:

getUser = () => {

    const that = this;
        .then(function (response) {
            // YOU WRITE IT
        }).then(function (json) {
            var body = JSON.parse(json.body);
            that.setState({userLogin: body.login});
        }).catch(function (ex) {
            // DISPLAY WITH LOGGER

Ultmately, your setState method will need to be more complicated than this, as there is more than just a login field to dispay.

Add a paragraph and button in the render method to display your input.

Make any necessary changes in App.js.

View the login name

Don’t forget Enzyme Debug:

Here are part of my header tests with the debug info:

describe('My Header tests', function () {
   import ElfDebugEnzyme from './ElfDebugEnzyme';
   const elfDebugEnzyme = new ElfDebugEnzyme(true, 'App.test.js');

    it('renders and reads H1 text', () => {
        const wrapper = shallow(<Header />);
        const welcome = <h2>Welcome to React</h2>;
        elfDebugEnzyme.getFirst(wrapper, 'h2');


Each Test Suite Gets Unique Name

Make sure each test suite you create has a unique and easy to understand name:

describe('My Get User Info Test', function () {...})

We need to be able to easily know where each failing test is located. Give the suite a good name, and it can help us quickly find the failing test so we can fix it:

My Get User Info Test › renders default message for state.userLogin


   Expected value to equal:


Make sure you have ESLint installed as part of all your projects:

npm install --save-dev eslint

Follow the steps in the ESLint assignment to set up .eslintrc.json and .eslintignore as necessary.

Turn it in

Commit, push. When you turn in the assignment, designate the directory in your repo where you did your work.

It would be good to tag your work just after you push an assignment. An ideal process:

  • add, commit, push. When you commit, include a message that mentions the assignment name.
  • tag, push. When you tag, include a message that mentions the assignment name.
  • create a branch with the name ReactPropsRefine.

You don’t have to use the branch, just create it. Then I can look in that branch for the code you submitted for the assignment. The branch would serve as a record of your project at the time your turned it in.

A reminder of how to tag:

$ git tag -a v3.0.? -m "Turning in ReactPropsRefine"
$ git push origin v3.0.?

The question mark stands for the next tag in your series of tags. For instance, on your system it might v3.0.4.


Don’t spend a lot of time fretting over whether or not this is the right architecture. I have several refactorings I want us to do as we add new features, but that is for next week. Just get this far.