Robin Ward
63f0247d21
FIX: Better height estimation / observing for menu panels
2015-09-16 14:46:53 -04:00
Régis Hanol
113cb4d3ad
FIX: '@observes' doesn't work that way
2015-09-08 10:34:36 +02:00
Sam
7a5c045399
its not a const anymore
2015-09-04 17:39:52 +10:00
Sam
6709eaeb3c
better have some sane upper bound here.
2015-09-04 17:23:37 +10:00
Sam
b3d6cefef4
FIX: never ask for less than 5 notifications
2015-09-04 17:22:26 +10:00
Sam
a54e8f3c5e
FEATURE: live refresh notifications as they happen
2015-09-04 13:20:33 +10:00
Robin Ward
e624b7198d
Try to estimate the amount of notifications to return based on height
2015-09-02 14:30:18 -04:00
Robin Ward
c36fdccab2
Add d-link component to simplify menu markup
2015-09-01 16:14:34 -04:00
Robin Ward
11b73e1fb7
Avoid calling Discourse.logout and use an action instead
2015-09-01 14:41:31 -04:00
Sam
a7eabade19
User import no longer needed
2015-09-01 21:48:05 +10:00
Sam
bbf3d772c4
use Discourse.logout, it works with SSO
2015-09-01 21:36:56 +10:00
cpradio
68659e834a
FIX: Fix the logout functionality in core
2015-08-31 18:39:19 -04:00
Robin Ward
ddf0db0338
Refactor notifications localStorage cache into adapter pattern.
...
Sometimes you want stale data right away, then refresh it async.
This adds `findStale` to the store for that case. If it returns
an object with `hasResults` you can get the `results` and display
them.
It also returns a `refresh()` method to freshen up the stale data.
To enable `localStorage` support for stale data, just include the
mixin `StaleLocalStorage` into an adapter for that model. This
commit includes a sample of doing that for `Notifications`.
2015-08-31 14:12:27 -04:00
Sam
41c32ea512
FEATURE: cache notifications in local storage
2015-08-30 09:50:08 +10:00
Robin Ward
3ae5a0a2df
UX: Merge notifications and user dropdown
2015-08-28 16:11:40 -04:00
