0f9e4da4ef
Trying to fix two issues: 1. Sometimes the publish_new! event for update_thread_original_message finishes running on the UI before the one for thread_created, in this case we just want to do nothing because thread_created will fetch the new thread along with its preview from the server if needed 2. Sometimes the thread GET and /read events were erroring because last_reply on the thread was nil, this was potentially occuring because the thread_created event was coming through to the UI before the rest of MessageCreator was done, so we just move that after the big update to set thread_id for the new and existing messages in the reply chain |
||
|---|---|---|
| .. | ||
| chat | ||
| discourse-details | ||
| discourse-lazy-videos | ||
| discourse-local-dates | ||
| discourse-narrative-bot | ||
| discourse-presence | ||
| poll | ||
| styleguide | ||