* When loading topics in bulk, only trigger state change callbacks after all the topics have been loaded and we determine that state has actually changed. * State change callbacks are also only triggered when state has changed. The use of JSON.stringify might raise some performance concerns here as this is a performance sensitive codepath. However, I measured the time for each `_setState` function call locally, by wrapping the function call with `performance.now()`, and did not see any significant overhead. |
||
|---|---|---|
| .. | ||
| badge-test.js | ||
| category-test.js | ||
| composer-test.js | ||
| email-log-test.js | ||
| group-test.js | ||
| invite-test.js | ||
| nav-item-test.js | ||
| pending-post-test.js | ||
| post-stream-test.js | ||
| post-test.js | ||
| private-message-topic-tracking-state-test.js | ||
| report-test.js | ||
| rest-model-test.js | ||
| result-set-test.js | ||
| session-test.js | ||
| site-test.js | ||
| staff-action-log-test.js | ||
| theme-test.js | ||
| topic-details-test.js | ||
| topic-test.js | ||
| topic-tracking-state-test.js | ||
| user-action-test.js | ||
| user-badge-test.js | ||
| user-drafts-test.js | ||
| user-stream-test.js | ||
| user-test.js | ||