This website requires JavaScript.
Explore
Help
Sign In
Mirror
/
zulip
mirror of
https://github.com/zulip/zulip.git
Watch
1
Star
0
Fork
You've already forked zulip
0
Code
Issues
Projects
Releases
Wiki
Activity
0d6f80059b
zulip
/
static
/
templates
/
subscriptions.hbs
4 lines
53 B
Handlebars
Raw
Normal View
History
Unescape
Escape
refactor: Render Stream Settings in two steps. We now render the "skin" part of "Stream Settings" before adding in the actual streams. The new function populate_stream_settings_left_panel() takes care of adding the streams. It uses a new template called `subscriptions.handlebars`. Splitting out this function will give us more flexibility for various improvements. First, we can decide to render the list after we open the overlay, just to avoid the problem that users don't know why the modal's opening. (And we could add a loader spinner as needed.) Second, we can improve our filter features so that we do filtering in the data instead of moving DOM rows around, which is expensive. Third, we can eventually introduce progressive rendering. Finally, having the function broken out will make profiling more precise about where bottlenecks exist.
2018-07-24 14:27:32 +02:00
{{
#
each
subscriptions
}}
templates: Use upstream Handlebars partials syntax. Signed-off-by: Anders Kaseorg <anders@zulipchat.com>
2019-07-11 04:05:28 +02:00
{{
>
subscription
}}
refactor: Render Stream Settings in two steps. We now render the "skin" part of "Stream Settings" before adding in the actual streams. The new function populate_stream_settings_left_panel() takes care of adding the streams. It uses a new template called `subscriptions.handlebars`. Splitting out this function will give us more flexibility for various improvements. First, we can decide to render the list after we open the overlay, just to avoid the problem that users don't know why the modal's opening. (And we could add a loader spinner as needed.) Second, we can improve our filter features so that we do filtering in the data instead of moving DOM rows around, which is expensive. Third, we can eventually introduce progressive rendering. Finally, having the function broken out will make profiling more precise about where bottlenecks exist.
2018-07-24 14:27:32 +02:00
{{
/
each
}}