PedroGeoGISdev wiki
  • Home
  • Linux OS
    • Linux: concepts
    • Linux: basic concepts
    • Linux: Bash
    • Linux: su and sudo
    • Linux: pipes
    • Linux: File System
    • Linux: Virtual Machines

    • Linux: distros
    • Linux Distros: Ubuntu
    • Linux Distros: Mint
    • Linux Distros: Debian
    • Linux Distros: openSuse
    • Linux Distros: Manjaro
    • Linux Distros: Red Hat Enterprise

    • Linux: laboratories
    • Linux Lab#LI01-1: Choose Linux
    • Linux Lab#LI01-2: Install at least three distributions
    • Linux Lab#LI01-3: Adjust user permissions
    • Linux Lab#LI02-1: Export env user with grep and pipe
    • Linux Lab#LI03-1: Manage users and groups
    • Linux Lab#LI03-2: Manage files
    • Linux Lab#LI03-3: Manage software
    • Linux Lab#LI03-4: Manage hardware
    • Linux Lab#LI04-1: Bash scripting, qtool
    • Linux Lab#LI04-2: Bash scripts as terminal tool
    • Linux Lab#LI04-3: Distribute the terminal app

    • Linux readings
    • Linux Resources
  • DevOps
    • What is DevOps
    • DevOps: Introduction
    • DevOps: Agile and Microservices
    • Infrastructure as code (IaC)
    • Immutable Infrastructure
    • Software Lifecycle

    • Documentation
    • How to document: Quarto and Obsidian

    • Network protocols
    • Network: Basics
    • Network: Client-server
    • Network Protocols
    • Network: DNS
    • Network: API Rest
    • Network: gRPC
    • Network: Websocket
    • Network: SMTP
    • Network: Ping
    • Network: UDP
    • Network: webhook
    • Network: SOAP
    • Network: graphQL

    • Version Control
    • Git
    • GitHub
    • Idea and GitHub 2023
    • Git and GitHub 2023 CLI

    • IDEs
    • IDE: Visual Code
    • IDE: IntellJIdea

    • DevOps tools
    • Amazon Web Services AWS
    • Docker
    • Jenkins pipelines
    • Kubernetes k8s
    • Digital Ocean
    • Nagios
    • Ansible

    • DevOps Laboratories
    • Lab 1: chat App
    • Lab 2: Spring Boot AWS AEB manually
    • Lab 3: Spring Boot and AWS S3 publisher
    • Lab 4: Spring Boot Docker/Jenkins
    • Lab 5: k8s on Digital Ocean
    • Lab 6: Spring Boot AWS codecommit

    • DevOps readings
    • DevOps Resources
  • MarkUp
    • MarkUp Languages
    • Introduction Markup
    • HTML Markup
    • Markdown Markup
    • Markdown and HTML working together, good idea?

    • Quarto Markdown
    • Quarto Markdown: basics
    • Quarto Markdown: creating
    • Quarto Markdown: publishing
    • Quarto Markdown: code & data
    • Quarto Markdown: api rest call
    • Quarto Markdown: OJS Cells
    • Quarto Markdown: cheat-sheet

    • Styling: CSS
    • Cascade Style Sheet
    • Cascade Style Sheet: Box Model and Containers
    • CSS: W3.css

    • MarkUp Languages Laboratories
    • Lab#MD01-1: Create and publish by Quarto

    • MarkUp Languages readings
    • MarkUp Languages Resources
  • Java SE
    • What is Java SE
    • Java Standard Edition: Basics
    • Java Standard Edition: Principles
    • Java MOOC Helsinki
    • Java MOOC Helsinki Syllabus

    • Java Create Project
    • Java SE: Maven
    • Java SE: Create Maven Project
    • Java SE: Project push GitHub
    • Java SE: JUnit and TDD

    • Java Concepts
    • Java SE: Class and Objects
    • Java SE: Scope
    • Java SE: static modifier
    • Java SE: Coupling and DDD
    • Java SE: Packages
    • Java SE: Abstract/Interface
    • Java SE: Java 8

    • Java Principles
    • Java SE: Encapsulation
    • Java SE: Abstraction
    • Java SE: Inherence
    • Java SE: Polymorphism

    • Java Design Patterns
    • Java Patterns: UML
    • Java Patterns: Types
    • Singleton
    • Factory
    • Abstract Factory
    • Builder
    • Facade
    • Bridge
    • Decorator
    • Composite
    • Observer
    • Strategy
    • State
    • Commander

    • Java SE Laboratories
    • Lab#SE00-1: Maven Person
    • Lab#SE00-2: Maven Clinic
    • Lab#SE00-3: Library Model
    • Lab#SE00-4: Abstract/Interface Human
    • Lab#SE01-1: Maven/Gradle Person and Account
    • Lab#SE01-2: Maven/Gradle Person and Account stored in JSON
    • Lab#SE02-1: Movie/Review, Model
    • Lab#SE02-2: Movie/Review, CRUD Operations
    • Lab#SE02-3: Movie/Review, factory
    • Lab#SE02-4: Movie/Review, interactivity and coupling
    • Lab#SE02-5: Movie/Review, simulate interactivity by console
    • Lab#SE03-1: Library/Book, Core-Model
    • Lab#SE03-2: Library/Book, Sprint Zero
    • Lab#SE03-3: Library/Book, Expand Model
    • Lab#SE04-1: healthyFood Restaurant, Core Model

    • Java SE readings
    • Java SE Resources
  • Python
    • Python Basics
    • Python: Basic Concepts
    • Python: Tips
  • JavaScript
    • JavaScript Basics
    • JavaScript: Basic Concepts
    • JavaScript: Tips
  • Spring
    • Spring Legacy
    • Spring Framework
    • Spring MVC
    • Springs Servlets

    • Spring Boot Basics
    • Spring Boot: fundamentals
    • Spring Boot: create a Project
    • Spring Boot: H2 DB and Thymeleaf
    • Spring Boot: cycle

    • Spring Boot Concepts
    • Spring Boot: Dependency Injection
    • Spring Boot: Annotations
    • Spring Boot: Controller
    • Spring Boot: View
    • Spring Boot: Thymeleaf
    • Spring Boot: Vaadin Flow
    • Spring Boot: Vaadin Hilla
    • Spring Boot: Model
    • Spring Boot: Rest
    • Spring Boot: Data & DB
    • Spring Boot: JPA & DI
    • Spring Boot: JPA Mappings
    • Spring Boot: JPA Relationships
    • Spring Boot: JPA Queries
    • Spring Boot: JPA Inherence
    • Spring Boot: Scaling

    • Spring Boot Laboratories
    • Lab#SB00-1: Library UML
    • Lab#SB00-2: CRUD User
    • Lab#SB00-3: LibraryManagement
    • Lab#SB00-4: API Rest
    • Lab#SB00-5: Rest & JPA-H2
    • Lab#SB00-6: Rest & MongoDB
    • Lab#SB00-7: Styling
    • Lab#SB01-1: DataBase
    • Lab#SB02-1: JPA Relationships
    • Lab#SB03-1: APIs & cloud
    • Lab#SB04-1: JPA Inherence
    • Lab#SB05-1: API Rest
    • Lab#SB06-1: employeeCourse
    • Lab#SB07-1: monitor Book
    • Lab#SB08-1: Restaurant UML
    • Lab#SB08-2: Vaadin
    • Lab#SB08-3: H2 and API Rest
    • Lab#SB08-4: JPA
    • Lab#SB08-5: Test API Rest
    • Lab#SB09-1: SpringIO Conference

    • Spring Boot readings
    • Spring Boot Resources
  • ReactJS
    • ReactJS: Principles
    • React JS: Introduction
    • React JS: render virtual DOM
    • React JS: Create a React project
    • React JS: Components
    • React JS: JSX
    • React JS: props and state

    • JavaScript: web scripting
    • JavaScript: basics
    • JavaScript: functions
    • JavaScript: objects
    • JavaScript: variables
    • JavaScript: flux control

    • ES6: ECMAScript 6
    • React JS ES6: arrow functions
    • React JS ES6: import modules
    • React JS ES6: array, data and key
    • React JS ES6: destructuring
    • React JS ES6: spread operator

    • ReacJS 18: Hooks
    • React JS: Rules of Hooks
    • ReactJS: useState
    • React JS: useReducer
    • React JS: useRef
    • React JS: useEffect
    • React JS: useContext
    • ReactJS: useMemo
    • ReactJS: custom hooks

    • ReactJS: Designing an App
    • React JS App: async
    • React JS App: events
    • React JS App: router
    • React JS App: conditional render
    • React JS App: styling

    • React JS: Laboratories
    • Lab#RE01-1: API Rest Axios
    • Lab#RE02-1: Router & Hooks
    • Lab#RE03-1: to-do app
    • Lab#RE03-2: HighCharts
    • Lab#RE03-3: API Rest Mono
    • Lab#RE03-4: API Rest Domains
    • Lab#RE03-5: data management
    • Lab#RE04-1: todo & server
    • Lab#RE04-2: Spring Boot & ReactJS
    • Lab#RE05-1: chat & websockets
    • Lab#RE05-2: chat: backend
    • Lab#RE05-3: chat & AWS
    • Lab#RE05-4: chat: test ws AWS
    • Lab#RE05-5: chat & front
    • Lab#RE05-6: chat & ws: front
    • Lab#RE06-1: healthyFood Restaurant
    • Lab#RE06-1-PR: create a pull request
    • Lab#RE07-1: traffic lights simulation

    • React JS readings
    • ReactJS Resources
  • Learning
    • Vocabulary
    • General Vocabulary
    • SCRUM Vocabulary
    • DevOps Vocabulary
    • Java SE Vocabulay
    • Spring Boot Vocabulary
    • DataBase Vocabulary
    • ReactJS Vocabulary
    • Web Vocabulary

    • Learning
    • Useful Questions
    • Learning: tips
    • Writing
    • Taking Notes
    • Comments
    • Document
    • Auto-Evaluate

    • Books & Articles
    • Books
    • Articles

    • What is SCRUM
    • SCRUM Agile Methodology
    • Agile Manifesto & Values
    • SCRUM Guide

    • Scrum Steps
    • Meetings, Impediments and Iterations
    • User stories, Tasks and Habits
    • Delivering Value & Communication
    • ScrumMaster, how it works
    • Mindset, the key to everything
    • Product Owner, how it works
    • Managing Time & Mind
    • Team & the Specialist
    • Albertus’ Dilemma
    • Before SCRUM
    • Team Dynamics
    • Emotions and Thoughts
    • Decision Making and Intuition
    • Beyond SCRUM
    • Balances, atmosphere and tools

    • Resources
    • SCRUM Resources
  • QGIS
    • QGIS basics
    • QGIS: basic concepts

    • QGIS laboratories
    • QGIS Laboratory 1: Introduction to Open Source GIS
  • ArcGIS Pro
    • ArcGIS Pro basics
    • ArcGIS Pro: basic concepts

    • ArcGIS Pro laboratories
    • ArcGIS Pro Laboratory 1: Getting Started
  • Bookmarks
    • Online Resources
    • Online Resources
  • About
    • About me and this site
    • About me
    • About this site
    • About images credit
  • Email
  • GitHub
  • LinkedIn
  1. React JS: Laboratories
  2. Lab#RE05-6: chat & ws: front
  • ReactJS

  • ReactJS: Principles
    • React JS: Introduction
    • React JS: render virtual DOM
    • React JS: Create a React project
    • React JS: Components
    • React JS: JSX
    • React JS: props and state

  • JavaScript: web scripting
    • JavaScript: basics
    • JavaScript: functions
    • JavaScript: objects
    • JavaScript: variables
    • JavaScript: flux control

  • ES6: ECMAScript 6
    • React JS ES6: arrow functions
    • React JS ES6: import modules
    • React JS ES6: array, data and key
    • React JS ES6: destructuring
    • React JS ES6: spread operator

  • ReacJS 18: Hooks
    • React JS: Rules of Hooks
    • ReactJS: useState
    • React JS: useReducer
    • React JS: useRef
    • React JS: useEffect
    • React JS: useContext
    • ReactJS: useMemo
    • ReactJS: custom hooks

  • ReactJS: Designing an App
    • React JS App: async
    • React JS App: events
    • React JS App: router
    • React JS App: conditional render
    • React JS App: styling

  • React JS: Laboratories
    • Lab#RE01-1: API Rest Axios

    • Lab#RE02-1: Router & Hooks

    • Lab#RE03-1: to-do app
    • Lab#RE03-2: HighCharts
    • Lab#RE03-3: API Rest Mono
    • Lab#RE03-4: API Rest Domains
    • Lab#RE03-5: data management

    • Lab#RE04-1: todo & server
    • Lab#RE04-2: Spring Boot & ReactJS

    • Lab#RE05-1: chat & websockets
    • Lab#RE05-2: chat: backend
    • Lab#RE05-3: chat & AWS
    • Lab#RE05-4: chat: test ws AWS
    • Lab#RE05-5: chat & front
    • Lab#RE05-6: chat & ws: front

    • Lab#RE06-1: healthyFood Restaurant
    • Lab#RE06-1-PR: create a pull request

    • Lab#RE07-1: traffic lights simulation

  • React JS readings
    • ReactJS Resources

On this page

  • 1 Step-by-step code
    • 1.1 SocketProvider.js
    • 1.2 Chat.jsx
    • 1.3 ChatRoom.jsx
    • 1.4 Conversation.js
  • Edit this page
  • Report an issue
  1. React JS: Laboratories
  2. Lab#RE05-6: chat & ws: front

Lab#RE05-6: chat & ws: front

ReactJS labs

reactjs
lab
Lab#RE05
labs
Author

albertprofe

Published

Tuesday, June 1, 2021

Modified

Sunday, August 10, 2025

📘 React JS Lab#RE05-6: chat & websockets

In this lab, we will be using:

  • the react-router-dom, which is a package with bindings for using React Router in web applications:
  • websockets, provided by ReactJS framework and:
    • useState
    • useEffect
    • useContext
  • AWS, Amanzon Web Services, architecture as a server-side:
    • Lambda
    • DynamoDB
    • API Gateway
    • Cloudwatch


Reference:

  • codesanbox myChat
  • myChat docs, backend & frontend

General architecture

General architecture

1 Step-by-step code

1.1 SocketProvider.js

SocketProvider.js
import { useState, useRef, useEffect, createContext } from "react";
import React from "react";

//https://developer.mozilla.org/en-US/docs/Web/API/WebSocket
//https://reactjs.org/docs/context.html
//ceate context we will use as store of websockets
export const WebsocketContext = createContext(false, null, () => {});
// ..........................................ready...message...send

// Make sure to put WebsocketProvider higher up in
// the component tree than any consumers
const SocketProvider = ({ children }) => {
  //two hooks to control states of connection and getting messages
  const [isReady, setIsReady] = useState(false);
  const [message, setMessage] = useState(null);

  //hook to control websocket persistence over
  // re-renders and component tree
  // to any consumer
  const websocket = useRef(null);
  // aws endpoint
  var protocol = "wss://";
  //var word = "no-connection";
  var word = "4rytv4evb2";
  var domain = ".execute-api.eu-central-1.amazonaws.com/test";
  var endpoint = protocol + word + domain;

  //hook to execute every render () => 
  //{ function, how many renders we want}
  // void > just one render at first
  //[] > every new state
  //[dependency] > depends on functions within dependency
  useEffect(() => {
    //create socket object
    const socket = new WebSocket(endpoint);
    //if we open, set isReady to true
    socket.onopen = () => setIsReady(true);
    //if we close, set isReady to false
    socket.onclose = () => setIsReady(false);
    //if we get a message, set message on that event (JSON)
    socket.onmessage = (event) => setMessage(event.data);
    websocket.current = socket;
    //close socket on return, that is, useEffect may use
    //this feature as optional, in this case we use it
    //to clean-up and close when exit the tab
    return () => {
      socket.close();
    };
  }, []);

  //create  variable JSON with the 3 websocket-states we will use
  //along the component tree: connection (isReady), 
  //get messages from server,
  //sendind messages : function
  const actionsWebSocket = [
    isReady,
    message,
    //function to send ws WHEN it is called
    websocket.current?.send.bind(websocket.current)
  ];

  //ending component: we call context => WebsoockettContext
  //so socket provider is a component which returns a context
  //And this context goes with explicit props: actionsWebSocket
  return (
    <WebsocketContext.Provider value={actionsWebSocket}>
      {children}
    </WebsocketContext.Provider>
  );
};

export default SocketProvider;

1.2 Chat.jsx

Chat.jsx
import React from "react";
import SocketProvider from "./SocketProvider";
import ChatRoom from "./ChatRoom";

export default function Chat() {
  return (
    <>
      <h1>Chat</h1>
      <hr />

      <SocketProvider>
        <ChatRoom />
      </SocketProvider>
    </>
  );
}

1.3 ChatRoom.jsx

ChatRoom component explanation

ChatRoom component explanation
  1. Declare function and export
  2. useContext: it just like a hook: useContext gets as initial value
    1. const [ready, message, send] = useContext(WebsocketContext);
  3. two useStates to control inpus from user: userId and chatId
    1. const [chatId, setChatId] = useState("");
    2. const [userId, setUserId] = useState("");
  4. Parse message JSON-aws (quasi JSON) from server to JSON and string
  5. Calculate boolean isLogin: let isLogin = messageString.length > 4;
  6. if-else with isLogin to print wether the user is logged or not
  7. function to send login data to server
  8. Packing props to tree-component downstairs
  9. Render
ChatRoom.jsx
import React from "react";
import { useContext, useState } from "react";
import { WebsocketContext } from "./SocketProvider";
import Conversation from "./Conversation";

export default function ChatRoom() {
  //use it just like a hook: useContext gets as initial value
  //the content WebSocketContext
  const [ready, message, send] = useContext(WebsocketContext);
  //two useStates to control inpus from user: userId and chatId
  const [chatId, setChatId] = useState("");
  const [userId, setUserId] = useState("");

  //just to parse message JSON-aws (quasi JSON) 
  //from server to JSON and string
  let messageToShow = "";
  let messageJSON = JSON.parse(message);
  const messageString = JSON.stringify(message);
  //console.log("messageJSON: " + messageJSON);
  //to print the connection after log in if it exists

  let isLogin = messageString.length > 4;
  if (!isLogin) messageToShow = "not logged-in";
  else
    messageToShow =
      messageJSON.action + 
      " (connectionId: " + messageJSON.connectionId + ")";

  //functio to send login data to server
  const sendLogin = () => {
    let data = {
      action: "login",
      chatId: chatId,
      userId: userId
    };
    if (ready) send(JSON.stringify(data));
  };

  //props to tree-component downstairs
  let props = {
    userId: userId,
    chatId: chatId
  };

  //view.......................................
  //conditional render.........................
  return (
    <>
      <div>
        <h3>Chat Room</h3>
        <p>
          Status connection: <b> {JSON.stringify(ready)}</b>
        </p>

        {ready && !isLogin ? (
          <>
            <label> UserId </label>
            <input
              type="text"
              placeholder="Alex"
              onChange={(e) => setUserId(e.target.value)}
            />
            <label> ChatId </label>
            <input
              type="text"
              placeholder="chatReactAWS"
              onChange={(e) => setChatId(e.target.value)}
            />
            <br />

            <button onClick={sendLogin}>Enter chat room</button>

            <p>
              Status log in: <b> {messageToShow}</b>
            </p>
          </>
        ) : (
          ""
        )}

        {isLogin ? <Conversation {...props} /> : ""}
      </div>
    </>
  );
}

1.4 Conversation.js

Conversation component explanation

Conversation component explanation
  1. Declare function and export
  2. useContext: it just like a hook: useContext gets as initial value
    1. const [ready, message, send] = useContext(WebsocketContext);
  3. declare useReducer to manage conversation states
  4. declare useState to manage text to print on screen from messages
  5. reducer: a reducer function called conversationReducer that handles different actions:
    1. When the action type is “send”, it creates a data object with information like action, chatId, userId, and text.
    2. If ready is true, it sends the data as a string.
    3. It then returns a new state array with a new message object appended.
    4. When the action type is “receive”, it parses the message and creates a new message object with properties like id, time, chatId, userId, and text.
    5. It returns a new state array with the new message object appended.
    6. When the action type is “login”, it parses the message and creates a new message object with properties like id, userId, time, and text.
    7. The text is constructed using different properties from the parsed message.
    8. It returns a new state array with the new message object appended.
    9. For any other action type, it simply returns the current state unchanged.
  6. useEffect: it runs when the message variable changes.
    1. It checks if the message does not contain the string “sent at”.
    2. If it doesn’t, it parses the message JSON and checks if the action property is “conversation”.
    3. If it is, it dispatches a “receive” action with the message as the payload; otherwise, it dispatches a “login” action.
    4. The variable isConverastion is used to track whether the message is a conversation.
    5. The final line logs the value of isConverastion and message to the console.
  7. Packing props to tree-component downstairs
  8. Render
  9. function ConversationsList
Conversation.jsx
import React from "react";
import { useContext, useState, useReducer, useEffect } from "react";
import { WebsocketContext } from "./SocketProvider";

export default function Conversation(props) {
  // use it just like a hook
  const [ready, message, send] = useContext(WebsocketContext);
  const [state, dispatch] = useReducer(conversationReducer, []);
  const [text, setText] = useState("");

  function conversationReducer(state, action) {
    switch (action.type) {
      case "send": {
        let data = {
          action: "conversation",
          chatId: props.chatId,
          userId: props.userId,
          text: action.payload
        };
        if (ready) send(JSON.stringify(data));

        return [
          ...state,
          {
            id: Date.now(),
            time: Date.now(),
            chatId: props.chatId,
            userId: props.userId,
            text: action.payload
          }
        ];
      }
      case "receive": {
        return [
          ...state,
          {
            id: Date.now(),
            time: JSON.parse(message).time,
            chatId: JSON.parse(message).chatId,
            userId: JSON.parse(message).userId,
            text: JSON.parse(message).text
          }
        ];
      }
      case "login": {
        return [
          ...state,
          {
            id: Date.now(),
            userId: "status",
            time: JSON.parse(message).time,
            text:
              JSON.parse(message).action +
              " at " +
              JSON.parse(message).time +
              " with connection:  " +
              JSON.parse(message).connectionId
          }
        ];
      }

      default: {
        return state;
      }
    }
  }

  useEffect(() => {
    var isConverastion = false;
    let stringMessage = JSON.stringify(message);
    if (!stringMessage.includes("sent at")) {
      isConverastion = JSON.parse(message).action === "conversation";
      if (isConverastion) dispatch({ type: "receive", payload: message });
      else dispatch({ type: "login", payload: message });
    }
    console.log("isConverastion: " 
      + isConverastion + " - message: " + message);
  }, [message]);

  let propsConversationLines = {
    state: state,
    userId: props.userId
  };

  return (
    <>
      <div>
        <h2>Conversation</h2>
        <hr />
        <div
          style={{
            color: "black",
            backgroundColor: "azure",
            padding: "10px",
            width: "400px",
            fontFamily: "Helvetica",
            fontSize: "13px"
          }}
        >
          <ConversationsList {...propsConversationLines} />
        </div>
        <br />
        <input
          type="text"
          name="content"
          placeholder="say hello"
          onChange={(e) => setText(e.target.value)}
        />

        <button onClick={() => 
          dispatch({ type: "send", payload: text })}>
          {" "}
          Send
        </button>
      </div>
    </>
  );
}

function ConversationsList(propsConversationLines) {
  return propsConversationLines.state.map((item) => (
    <>
      {propsConversationLines.userId === item.userId ? (
        <p
          style={{
            textAlign: "right"
          }}
        >
          {item.userId}: {item.text}
        </p>
      ) : (
        <p
          style={{
            textAlign: "left"
          }}
        >
          {item.userId}: {item.text}
        </p>
      )}
    </>
  ));
}
Back to top
Lab#RE05-5: chat & front

This website is built with Quarto.

Difficulties are just things to overcome, after all. Ernest Shackleton

  • Edit this page
  • Report an issue