mirror of
https://github.com/discourse/discourse.git
synced 2024-12-12 08:43:44 +08:00
90efdd7f9d
This commit starts from a simple observation: cooking messages on the hot path can be slow. Especially with a lot of mentions. To move cooking from the hot path, this commit has made the following changes: - updating cooked, inserting mentions and notifying user of new mentions has been moved inside the `process_message` job. It happens right after the `Chat::MessageProcessor` run, which is where the cooking happens. - the similar existing code in `rebake!` has also been moved to rely on the `process_message`job only - refactored `create_mentions` and `update_mentions` into one single `upsert_mentions` which can be called invariably - allows services to decide if their job is ran inline or later. It avoids to need to know you have to use `Jobs.run_immediately!` in this case, in tests it will be inline per default - made various frontend changes to make the chat-channel component lifecycle clearer. we had to handle `did-update @channel` which was super awkward and creating bugs with listeners which the changes of the PR made clear in failing specs - adds a new `-processed` (and `-not-processed`) class on the chat message, this is made to have a good lifecyle hook in system specs |
||
|---|---|---|
| .. | ||
| chat-channel-archive.js | ||
| chat-channel.js | ||
| chat-chatable.js | ||
| chat-direct-message.js | ||
| chat-message-reaction.js | ||
| chat-message.js | ||
| chat-notice.js | ||
| chat-thread-preview.js | ||
| chat-thread.js | ||
| chat-tracking-state.js | ||
| user-chat-channel-membership.js | ||
| user-chat-thread-membership.js | ||