Welcome to ReactGitMenu

React Git Menu

The goals of this assignment are:

In this serious of screen shots you can see the menu, and the various views it provides. In particular, each view features one component, or one component and its child components. This is a SPA, or Single Page App.

Git View

IMAGE: Home page with styling and menu at bottom of header.

Bar Foo

IMAGE: Micro page with menu no styling.


IMAGE: Get Foo page with menu styling and menu at top.

The components folder

IMAGE: The components folder

Install React Router

Read the React Router Dom Install section from Elvenware then return to this document and install react-router-dom in the client directory.

Rename Header to ElfHeader

In this assignment we will be working the component that we use to display our header. We initially called this class Header. Let's do a small refactor here and change its name to ElfHeader. This will make it less likely that its name will collide with the HTML tag of the same name, or some other JavaScript variable with the same name.

I prefer to use Git to rename files:

git mv src/components/Header.js src/components/ElfHeader.js

Then open up the file and change the name of the class itself from Header to ElfHeader:

class ElfHeader extends Component { ... }

export default ElfHeader;

The Main Index

Recall how our modified index.js file looks:

import React from 'react';
import ReactDOM from 'react-dom';
import App from './components/App';
import './css/index.css';


NOTE: Notice how easy it is for us to move classes and views around when we use the React architecture. The small, focused loosely coupled components that we have created give us the flexibility to accept changes in specifications with a minimum of disruption.


We are going to fundamentally change the structure of our program. This means making changes to this JSX in App.js:

<div className="App">
    <ApiFoo appInit={appInit}/>

Add Menu

Let's add in the code in ElfHeader that defines the "visible" menu that the user will click on:

import {Link} from "react-router-dom";

class ElfHeader extends Component {
    render() {
        return (
            <div className="App">
                <header className="App-header">
                                <Link to="/">Git User</Link>
                            // YOU WRITE LINKS FOR MICRO & APIFOO
                    <img ...>
                    <h1 ...>

export default ElfHeader;

Here we are using the react-router-dom class called Link to help us create a link that behaves appropriately in this context. It will, for instance, turn the first two items into code that looks like this at run time:

<li><a href="/">Home</a></li>
<li><a href="/api-foo">ApiFoo</a></li>

Testing ElfHeader

We should wrap our Header in a MemoryRouter when doing the renders without crashing test:

import {MemoryRouter} from "react-router-dom";


it('renders without crashing', () => {
    const div = document.createElement('div');
    ReactDOM.render(<MemoryRouter><ElfHeader /></MemoryRouter>, div);

Defining Routes

The final step involves defining what the application will do when the user clicks on a particular menu item. Here is the basic structure:

import {BrowserRouter, Route} from "react-router-dom";

class App extends Component {
    render() {
        return (
                <div className="App">
                    <Route exact path="/" component={GitUser}/>
                    // YOU WRITE APIFOO AND MICRO

We do it like this for the home menu:

<Route exact path="/" component={GitUser}/>

Note the user of the flag exact. This is necessary because a simple match on '/' will pass both '/' and '/api-foo'. In fact, it will match any URL beginning '/'. So we tell the router that we want an exact match.

I want you to have to figure out at least one of these routes on your own, so I will let you discover the solution for creating the Route to GetFoo. It isn't hard, so try not to over-complicate it.

The normal pattern is to define the path, and then the component:

<Route path="/my-component" component={MyComponent}/>

You cannot, however, pass props to MyComponent the same way you can elsewhere in a React application. Instead, you use render instead of component, and the syntax looks like this in our case:

<Route path="/api-foo"
    render={(props) => (
        <ApiFoo {...props}
            appInit={appInit} />

We use this syntax because react-router-dom passes a certain number of props to a component by default, and we don't want to lose them. Here we use the spread-operator to pass the Router props and then we pass our own props.

Here is what it looks like in the debugger when working with a different component than the one we use in program:

Local Scope Props Numbers

IMAGES: You can see the Sources tab of Chrome Developer Tools

I've run to a breakpoint on line 10 of SmallNumbers.js. At the bottom right we can see that props for SmallNumbers is in the Local Scope. The debugger displays our Numbers prop, along with three properties passed by the react-router-dom:

They can come in useful in more advanced scenarios than the one we see here. In particular, they can help preserve history so the user can move back and forth through your site.

Style the Menu

Read about it here

Show All Fields of Git User

Be sure to replace the field-definitions.js file with new code from the Git Convert assignment. You should be able to display all the fields that are returned from Git.

You will need to make some edits here to the string that is assignment to the value attribute:

<ElfElements {...field}

I ended up calling a function and doing my work there:


In the getValue function, you might want to use syntax like this:

return testMe || ''

That code will return an empty string if testMe is null or undefined. You will also need to handle the case with gitUser[field.id] is a boolean.

When everything is working right, you won't see messages like this in the debugger: Warning: value prop on input should not be null. Consider using the empty string to clear the component or undefined for uncontrolled components. Also, your boolean fields such as site-admin will have strings in them rather than being blank. The point being, of course, that your code should run without warnings or errors.

Turn it in

Add, commit, push, tag and/or branch. Let me know the tag and/or branch as well as the directory for your work. Make sure all your tests pass. For now.