03d32f26bb
Recent changes surfaced the various issues with this codepath: - we were not correctly reseting `messageLookup` leading to us trying to scroll to a non existing message in the view - we were calling markAsRead which would scroll to the bottom, even if we had a target message - we were not debouncing fetchMessages, which could cause multiple reload of the messages when loading it with a targetMessageId: first fetch from last read and then immediately fetch from targetMessageId - other naming inconsistencies - not handling drawer This commit also adds tests for classic scenarios related to this use case. |
||
|---|---|---|
| .. | ||
| adapters | ||
| components | ||
| connectors | ||
| controllers | ||
| helpers | ||
| initializers | ||
| lib | ||
| models | ||
| modifiers/chat | ||
| pre-initializers | ||
| routes | ||
| services | ||
| templates | ||
| widgets | ||
| admin-chat-route-map.js | ||
| chat-route-map.js | ||
| preferences-chat-route-map.js | ||