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.

Sign up for GitHub

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

Jump to bottom

Migrate Message Data structure to hashmap #232

Open
AlexanderWangY opened this issue Aug 30, 2024 · 1 comment
Open

Migrate Message Data structure to hashmap #232

AlexanderWangY opened this issue Aug 30, 2024 · 1 comment
Assignees
@AlexanderWangY
Labels
Frontend 🖥 Issues corresponding to the frontend/client. Hard You should be an active contributor to work on this issue Improvement Important changes made that are not described by an optimization or refactor

Comments

@AlexanderWangY
Copy link
Collaborator

As of now, all incoming messages are stored in an array. However this is inefficient and also hard to play around with (especially with replies and reactions). Therefore we need to migrate to a hashmap Map<Key, Value> where Key is the messageID and the value is the message.

Please also make it in chronological order please so the chat is normal :)
@AlexanderWangY AlexanderWangY added Frontend 🖥 Issues corresponding to the frontend/client. Hard You should be an active contributor to work on this issue Improvement Important changes made that are not described by an optimization or refactor labels Aug 30, 2024
@AlexanderWangY AlexanderWangY self-assigned this Sep 6, 2024
@KOrtizLedezma
Copy link
Contributor

Can I get this one assigned?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@AlexanderWangY AlexanderWangY

Labels
Frontend 🖥 Issues corresponding to the frontend/client. Hard You should be an active contributor to work on this issue Improvement Important changes made that are not described by an optimization or refactor
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@KOrtizLedezma @AlexanderWangY