Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature: Utilize Message Read Status for Message Icon Badge #427

Closed
leekahung opened this issue Sep 15, 2023 · 1 comment
Closed

Feature: Utilize Message Read Status for Message Icon Badge #427

leekahung opened this issue Sep 15, 2023 · 1 comment
Assignees
Labels
good first issue Good for newcomers new feature New feature or request

Comments

@leekahung
Copy link
Contributor

Utilize Message Read Status for Message Icon Badge


Feature Description:

With the read status now implemented, we could now utilize the read status from Messages for something like an icon badge to indicate there are unread messages.


Use Case:

See above.


Proposed Solution:

Given that read status would be utilizing the value true (or 1) for read, we could have a badge appear when number of message !== total sum of read status true as one potential solution.

Another solution to this would be to utilize the false state (or 0) and have the badge appear as long as there's a read status that's false from the list of messages. We could use utility functions like .every() or .some() for this purpose depending on the type of logic the developer wish to employ.


Additional Context:

Please provide any other information that might be helpful.

@leekahung leekahung added new feature New feature or request good first issue Good for newcomers labels Sep 15, 2023
@leekahung leekahung changed the title Utilize Message Read Status for Message Icon Badge Feature: Utilize Message Read Status for Message Icon Badge Sep 15, 2023
@timbot1789 timbot1789 assigned timbot1789 and unassigned timbot1789 Oct 4, 2023
@TheChunkyPumpkinhead TheChunkyPumpkinhead self-assigned this Oct 4, 2023
@leekahung
Copy link
Contributor Author

New feature has been merged into Development. Resolving issue #427 as completed. Reference to #454 for bug related to PR #437.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers new feature New feature or request
Projects
None yet
Development

When branches are created from issues, their pull requests are automatically linked.

3 participants