xynree / hatchways-messenger

A one-to-one realtime chat app with integration to Cloudinary Image API.

Messenger

A one-to-one realtime chat app. Functionality added for assessment from Hatchways.io.

My Contributions

Bug Fix: Sending/Loading Messages

Adjusted posting function to handle a promise asynchronously with async/await. Changed new message functions to functionally map to fresh state variables instead of mutating state. Messages sort with Moment.js functions at the fetch before mapping to message UI.

Feature: UI Implementation

Login and Signup pages are set up to match the Figma spec provided in #3 Issue.

Feature: Image Messaging

UI displays a preview attachment image for uploading a file before submitting a POST request to upload the image to a Cloudinary host. The image sent in the chat display message includes a functional modal to view at a larger size.

hatchways-messenger's Issues

Feature: Sending images - front end

THIS ISSUE WAS AUTOGENERATED BY HATCHWAYS
We would like for users to be able to send images. We would like you to implement the front end of this feature. The backend functionality is already implemented. This feature is described in depth on this page. Please do not use an external library to implement this feature.

In your PR description, please explain a couple different ways we could have handled the UX for attaching an image for this feature. What are the benefits and drawbacks of each?

Bug fix: Sending messages

THIS ISSUE WAS AUTOGENERATED BY HATCHWAYS
There are some bugs in our starting code that we would like you to investigate and resolve. First, when you send a new message, it does not immediately appear on the screen. We would like new messages to be immediately added to the chat UI for both existing conversations and new conversations. (Note: This may require more than one change)

Additionally, messages are not displayed in the correct order on page load. Messages should be displayed in order with the oldest messages at the top and newest messages at the bottom.

The starting code has some Cypress tests for this ticket (bug-fix-ticket.spec.js). Please ensure that your code passes these tests before requesting review on your PR for this feature (the README has details on how to run the tests).

All fixes for these bugs can be done on the front end. In your PR description, please share the steps you followed to debug this issue. What tools did you use?

Feature: New design for login/signup pages

THIS ISSUE WAS AUTOGENERATED BY HATCHWAYS
We’ve received new specs from our designer. Please implement the design for the login and signup pages, and make it mobile responsive. The design spec and needed assets are available in this zip folder, as well as in this Figma file. The spec may need a bit of adapting to fit our use case, so please use your best judgement. Also note that the resources provided include more than just the login and signup pages, but only these two pages should be implemented for this ticket.

Please include a couple of screenshots in the description when making this PR to showcase the styling you've done.

In your PR description, please explain a couple different ways we could have handled code organization for this feature. Are there the benefits and drawbacks for each?