Glasgow | 26-Jul-SDC | Shreef Ibrahim | Sprint 2 | chatApp

[shreefAhmedM]

Self checklist

• I have titled my PR with Region | Cohort | FirstName LastName | Sprint | Assignment Title
• My changes meet the requirements of the task
• I have tested my changes
• My changes follow the style guide

Task code

CYF-1162

Changelist

A real time chat application with a Node.js/Express and WebSocket backend and a frontend chat interface. Added message history, real-time messaging, likes/dislikes, scheduled messages,... Also added Docker support for deployment.

Deployed frontend:

Deployed backend:

[LonMcGregor]

Good work, this app is well written and has lots of functionality. I do have some questions about your implementation for you to answer, however.

[LonMcGregor]

I noticed it was possible for me to run the app before I started the backend - why is that possible?

[shreefAhmedM]

Yes, that's true because the frontend is a separate application from the backend, so when you open the frontend, it will run and try to connect to the backend and if the connection fails it will display an appropriate message to the user. So the app can open and display the UI, but the actual chat functionality will not work properly without the backend.

[LonMcGregor]

Have you tried testing liking an old message when there are newer ones below it? Does this approach to handling updated work correctly?

[shreefAhmedM]

Yes, I see the issue when I click the like button updateMessage() function removes the old message by using "existing.remove()". And then add the message "addMessage(message);" instead of just finding the existing message and updating only its like/dislike buttons

I have updated, thank.

[LonMcGregor]

Great, the chat app seems to be working well now. Good work