adlascio / 8e65a6 Goto Github PK

THIS ISSUE WAS AUTOGENERATED BY HATCHWAYS
We want to track for each message if it has been read by the recipient, and to make several front end UI updates with this information, such as displaying how many unread messages there are in a given conversation.

You can reference the spec in this Figma file for the various updates to be made to reflect unread messages. (Note that the Figma file includes more than just the spec needed for this feature). Please include a screenshot in your PR description showing your updated UI.

In your PR description, please explain a couple different ways we could have stored the read status in the database for this feature. What are the benefits and drawbacks of each?

THIS ISSUE WAS AUTOGENERATED BY HATCHWAYS
Currently, our app only allows conversations between two users. We would like to allow conversations with groups of 3 or more users. This ticket is not to implement this full change, but to help us plan out what that change would look like. Please make a PR with the changes to just the database models that you would use to implement this feature. Please include "draft" in the title of the PR. Then, in the PR description, write out notes to answer the following two questions:

1. What additional (non-database) changes are needed to implement this feature (we want this to be high level but thorough)?

2. If our app were already deployed, what steps would we need to take to move to this new feature without disrupting service for current users?

In your PR description, please explain a couple different ways we could have designed the database for this feature. What are the benefits and drawbacks of each?

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. Messages should be displayed without needing to refresh the page first. 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.

As part of your score for this ticket, we consider how long you spend finding and solving the bugs. Please post on slack as soon as you identify the cause of each bug as well as once you’ve implemented a fix for each bug. Similar to a bug in a real work setting, the faster this is solved the better. However, the bugs need to be fixed regardless of time, so take as long as needed to find and fix both bugs before making a pull request. Note that we only consider the time between when you receive this issue and when you request review on a pull request solving both issues, not the time it takes for the pull request to be reviewed or addressing any feedback on the initial pull request.

In your PR description, please share the steps you followed to debug this issue. What tools did you use?