Photo by on
This is the second part of a thorough step-by-step guide for building a single page chat application using React, TypeScript and Socket.io. If you want to take a look at the other chapters, here you go:
If you want to skip the reading, 💁 is the GitHub repository with a detailed 🙌, and you can check the live demo. 🎀 In order to play with it, you need to open it in two different browsers (or browser tabs) or devices (you may use your computer and your smartphone) and chat with each other.🎀
More detailed planing
In this section we need to have a deeper look at our application and define what would be the building blocks of it. Since we are going to use React and we know that in the React world the term component is widely used, we may refer to our building blocks as components. We will have components responsible for purely visual stuff, as well as such for managing the local storage for example.
Let's try to imagine mentally how our app will look in the end and what would be the components it will need. What we already know is this:
We will need a http server that will take care of starting the server and handling interactions with Socket.io (sending and receiving messages). Our server logic will be simple enough to live in only one file. You can see the actual implementation .
Here we need to have all the visual controls, plus means for managing interactions with local storage, where we will save the user preferences, as well as handling of the translations and color themes.
Now it is a good moment to point out that for implementing the functionality in the app, I have used . Also, since I knew I will have to deal with , I did of "research-test-play" trip. And the output of it was that I already had a , which provides all the functionalities I needed.
Another thing you will notice when looking at the folder is, that every component has its own directory with a few files in it. These files serve the following logic:
index.ts → entry point, just expose the component itself, this helps for not having to write repeatedly and long import statements. Here is an example:
// Instead of having to write this: import ChatArea from '../../ChatArea/ChatArea'; // We can have just this: import ChatArea from '../../ChatArea';
.tsx(e.g. ChatArea.tsx) → actual component implementation live here. .test.tsx(e.g. ChatArea.tsx) → unit tests of the component live here. .tsx(e.g. StyledChatArea.tsx) → CSS styles of the component live here.
The same pattern is used for most of the components, exception are only the pages, i.e. the components which play the role of parents for all the inner parts - and .
So, with that said, I think we can see what would be our application structure when we try to "componentize" it. Here a list of the components I came up with:
Note: all namings are a matter of personal choice, feel free to name yours as you wish.
Let me try to give you a bit more detailed explanation for each of them below:
- - contains the main app routing logic, i.e. here we define the app routes by giving them path and component to load when this path is reached. Uses package.
- - represents the main chat area, where all the message are being displayed. It's responsible also for auto scrolling down when the visible area limit is reached.
- - responsible for displaying controls allowing the user to select the time display mode -12h or 24h. It uses a common component called (will describe it below) and the Local Storage service to write/read from the browser's local storage.
- - this is a common component, built with the idea to be re-usable all over the app. We use this component in a few other components, such as ClockModeSelector, and . It contains logic for displaying two radio buttons with possibility to pass a callback function which will execute certain action depending on your needs.
- - responsible for displaying a select input control for choosing the app language. It accepts a function that is coming from the utility and does the actual language change.
- - this component is responsible for displaying each chat message, sent or received. It includes the nickname of the sender and timestamp showing the time when the message was sent/received. It also provides support for emojis (e.g. ❤️) and links parsing - see the screenshot below.
- - this is component that provides the necessary user interface controls for sending messages - a text input field and a Send button. It contains logic for defining the different ways of sending - via click or key press (with ENTER or CTRL+ENTER), as well as clearing the input field when a new message is sent.
- - here lives the implementation of the app navigation. It consists of two tabs - Chat and Settings and contains logic for connecting to sockets, by sending a when the component is mounted. It manages an component by passing it the count of the currently unread messages (this happens when the user receives a message while being on the Settings page). It also has a logic responsible for making the tab blinking when a new message arrives.
- - this is simple component for rendering the nickname of a chat user.
- - this would be a simple component, used in Settings page for rendering a Reset button, which function is going to be exactly that - resetting the settings selections that are already saved into the local storage, if any.
- - responsible for displaying options for choosing if a message can be sent via CTRL+ENTER. It works same way as ClockModeSelector component - uses RadioGroup component and accepts a callback function.
- - same as the component above. The only difference is that here the user is allowed to select a color theme. In our case the options are only two - light theme or dark theme.
- - simple component used for rendering the time of the messages.
- - this is the component I mentioned a little bit earlier. It shows a counter indicating the number of the received, but not yet read messages. It's positioned in the navigation area.
- - this the component responsible for rendering an input field the user can use for changing its user name. It's saving the new user name into the local storage, using a function. This means that the actual triggering of the function is happening some defined time after the user stops typing. It also triggers another Redux action, so we can be able to use the new username in our Redux state.
- - parent component that enclose everything shown on the Chat page.
- - parent component that enclose everything shown on the Settings page.
Everything described above was related to our React components. All of them are responsible for getting some data and displaying it in a proper way. In order to be able to handle this data in a convenient for us way, we use a few more things. Let's have a look at these things in the next chapter of this tutorial.
🔥 Thanks for reading! 🔥