mirror of
https://github.com/status-im/status-go.git
synced 2025-01-09 22:26:30 +00:00
Andrea Maria Piana
ab01a05cd6
Don't use bytes anymore for LastMessage
LastMessage in chat was encoded in bytes so that we don't have to encoded/decode everytime we save to db or pass the client. An issue with emoji surfaced a problem with this approach. Chat.LastClockValue represent the last clock value of any type of message exchanged in a chat (emoji,group membership updates, contact updates). So when receving a new message, we should update LastMessage if the clock of the LastMessage is lower than the received message, and we should not only check LastClockValue, otherwise the message might be discarded although it is the most recent. This commit fixes the issue by keeping LastMessage as an object and comparing LastMessage.Clock instead of LastClockValue
Status bindings for go-ethereum
Docs
- How to Build
- How to Contribute
- How to Release
- How to run a Bootnode
- How to run a Mailserver
- How to run a Waku node
- How to configure status-go
License
Description
Languages
Go
98.6%
Python
0.7%
Shell
0.4%
Makefile
0.1%
Groovy
0.1%