fc1fd1b416
In order to include the new/unread count in the browse more message under suggested topics, a couple of technical changes have to be made. 1. `PrivateMessageTopicTrackingState` is now auto-injected which is similar to how it is done for `TopicTrackingState`. This is done so we don't have to attempt to pass the `PrivateMessageTopicTrackingState` object multiple levels down into the suggested-topics component. While the object is auto-injected, we only fetch the initial state and start tracking when the relevant private messages routes has been hit and only when a private message's suggested topics is loaded. This is done as we do not want to add the extra overhead of fetching the inital state to all page loads but instead wait till the private messages routes are hit. 2. Previously, we would stop tracking once the `user-private-messages` route has been deactivated. However, that is not ideal since navigating out of the route and back means we send an API call to the server each time. Since `PrivateMessageTopicTrackingState` is kept in sync cheaply via messageBus, we can just continue to track the state even if the user has navigated away from the relevant stages. |
||
|---|---|---|
| .. | ||
| acceptance | ||
| fixtures | ||
| helpers | ||
| integration | ||
| unit | ||
| core_plugins_tests.js | ||
| index.html | ||
| plugin_tests.js.erb | ||
| setup-tests.js | ||
| test_helper.js | ||
| test_starter.js | ||
| test-helper.js | ||
| theme_qunit_ember_jquery.js | ||
| theme_qunit_helper.js | ||
| theme_qunit_tests_vendor.js | ||
| theme_qunit_vendor.js | ||