1bdb42b67e
Sometimes a conversation's messages would be reverse-ordered on first load, correcting themselves after a refresh. This is an artifact of the order we load messages from the database. To fix, load them in the opposite order. The alternative solution would be to reset the collection every time we fetch new messages, but this would create an entirely new set of model objects each time, which seems unnecessary. |
||
|---|---|---|
| .. | ||
| conversations.js | ||
| messages.js | ||