DEV Community

Cover image for My own realtime chat with react, graphql and postgresql [part 6 - React setup]
David Alejandro Quiñonez
David Alejandro Quiñonez

Posted on

My own realtime chat with react, graphql and postgresql [part 6 - React setup]

In the following parts we are going to configure the client, the react app that will consume the api we built previously.

I would recommend to initialize the project with create-react-app, running npx create-react-app myFrontend on the console (npx comes with npm 5.2+)

We can start with the project structure. I'll use the containers/components pattern, this means centralize the state by a group of 'containers' and print in the dom some fabulous things with the 'components'.

For this project I built a Login and a Chatroom containers. We'll be seeing deep down that code in a bit.

Also we'll need a guarded routing system in order to prevent the access of not logged users to the chat. For this I'll use react-router, you can install with npm install react-router-dom.

For the styles I'll use sass, you can check out how to implement this here.

So let's start coding!

First of all let's build the routing system.


import Login from "../containers/Login/Login";
import Chatroom from "../containers/Chatroom/Chatroom";

const appRoutes = [
  { path: "/login", component: Login },
    path: "/chatroom",
    private: true,
    component: Chatroom,
  { redirect: true, path: "/", to: "/login" },

export default appRoutes;

Enter fullscreen mode Exit fullscreen mode

The appRoutes array is composed by objects that have path, component, and a private attribute. The redirect flag will allow the react-router to match the root paht / to login and vice versa.


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

const PrivateRoute = ({ component: Component, to, key }) => {
  const shallPass = false;
  return (
      render={(props) =>
        shallPass ? <Component {...props} /> : <Redirect to="/" />

export default PrivateRoute;
Enter fullscreen mode Exit fullscreen mode

This utility component will use a flag shallPass to let a user see the component or redirect to the root. For now, we define the flag as false, but it will be related to the login process.


import React from "react";
import { Route, Switch, Redirect } from "react-router";
import PrivateRoute from "./utils/PrivateRoute";

const AppRouter = ({ routes }) => {
  return (
      {, key) => {
        if (prop.redirect)
          return <Redirect from={prop.path} to={} key={key} />;
        if (prop.private)
          return (
        return <Route path={prop.path} component={prop.component} key={key} />;

export default AppRouter;

Enter fullscreen mode Exit fullscreen mode

Lets analize this router:

  1. We will use a routes array as a prop. This array has the same properties as the app.routes.js.
  2. Using the Redirect component from react-router we can show the component depending on the redirect flag.
  3. Depending on the private flag we use the PrivateRoute guard to secure the navigation.


import React from "react";
import { HashRouter } from "react-router-dom";
import AppRouter from "./AppRouter";
import appRoutes from "./routes/app.routes";

const App = () => {
  return <div className="App">
     <HashRouter basename="/">
        <AppRouter routes={appRoutes} />

export default App;

Enter fullscreen mode Exit fullscreen mode

Let's break this code a little bit:

  1. Using HashRouter we add a base path '#', this is useful if we're going to deploy our frontend in some third party hosting service because of the routing they may have implemented. If you are using your own hosting you could use the BrowserRouter.
  2. As we saw in the AppRouter it recives a routes property, this routes are composed by a pair of path and component so our routing sytem know what to render.

If we run npm start you won't be able to see anything, actually you may have some errors, this is because you haven't created the Login and Chatroom containers. In the next part we will start with the Login container and the graphql petitions.

Top comments (0)