mirror of
https://github.com/discourse/discourse.git
synced 2024-11-29 00:55:06 +08:00
bf64a184ea
Context of the problem When viewing the topic list for either the personal inbox or the group PM inbox, we store a cache of the topic list if the user has loaded more topics in the topic list. This cache is used to improve the experience for users so that navigating to a topic and then back would not make them lose their "last read" position in the topic list. Without this cache, users will have to start from the top of the topic list each time they navigate back after reading a topic. What is the problem? After archiving a PM, the user is redirected to either the personal inbox or the group PM inbox. The problem is that if a topic list cache exists, we will render the topic list using the cache. However, this means that the archived PM will still appear in the list leading to confusion for our users. What is the fix? To fix this, we will simply clear the topic list cache after a user archives a topic. |
||
|---|---|---|
| .. | ||
| admin | ||
| bootstrap-json | ||
| confirm-new-email | ||
| dialog-holder | ||
| discourse | ||
| discourse-common | ||
| discourse-hbr | ||
| discourse-plugins | ||
| discourse-widget-hbs | ||
| docs | ||
| ember-addons | ||
| ember-cli-progress-ci | ||
| ember-production-deprecations | ||
| locales | ||
| patches | ||
| pretty-text | ||
| select-kit | ||
| truth-helpers | ||
| wizard | ||
| .licensee.json | ||
| .npmrc | ||
| discourse-js-processor.js | ||
| handlebars-shim.js | ||
| package.json | ||
| polyfills.js | ||
| service-worker.js.erb | ||
| yarn.lock | ||