Mirror
/
zulip
mirror of https://github.com/zulip/zulip.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
zulip/static/js/bundles/app.js

233 lines
6.8 KiB
JavaScript
Raw Normal View History

bundles: Rename commons.js to common.js. Signed-off-by: Anders Kaseorg <anders@zulipchat.com>
2019-07-03 01:53:08 +02:00
import "./common.js";
webpack: Transition app.js to be compiled by webpack. This commit moves all files previously under the 'app' bundle in the Django pipeline to being compiled by webpack under the 'app' entry point. In the process, it moves assets under the app entry to a file called app.js that consumes all relevant css and js files. This commit also edits the webpack config to be able to expose certain variables for third party libraries that are currently required by some modules. This is bad coding form and should be refactored to requiring whatever dependencies a module may have; we're just deferring that to the future to simplify the series of transitions we need to do here. The variable exposure is done using expose-loader in webpack. The app/index.html template is edited to override the newly introduced 'commonjs' block in the base template. This is done as a temporary measure so as not to disrupt other pages on the app during the transition. It also fixes the value of the 'this' context that was being inferred as window by third party libraries. This is done using imports-loader in the webpack config. This is also messy and probably isn't how we want things to work long term.
2018-05-28 08:09:49 +02:00
// Import Third party libraries
webpack: Remove resolve.modules override. The minimal syntactic sugar it might provide isn’t worth the unexpected side effects (including side effects on third party modules). For now, we allow zrequire to emulate the previous syntax in the Node test suite, even though stealing part of the NPM namespace is confusing. Signed-off-by: Anders Kaseorg <anders@zulipchat.com>
2019-06-21 01:59:21 +02:00
import "../../third/bootstrap-notify/js/bootstrap-notify.js";
webpack: Rectify "common" bundle with bundles/commons.js. Moving bootstrap-typeahead from bundles/commons.js to bundles/app.js and csrf.js from bundles/app.js to bundles/commons.js makes bundles/commons.js equivalent to the "common" bundle, so we can replace the latter with the former. Signed-off-by: Anders Kaseorg <anders@zulipchat.com>
2019-06-29 08:06:33 +02:00
import "../../third/bootstrap-typeahead/typeahead.js";
third: Get jquery-caret-plugin from NPM. Signed-off-by: Anders Kaseorg <anders@zulipchat.com>
2019-07-02 01:25:03 +02:00
import "jquery-caret-plugin/src/jquery.caret.js";
webpack: Remove resolve.modules override. The minimal syntactic sugar it might provide isn’t worth the unexpected side effects (including side effects on third party modules). For now, we allow zrequire to emulate the previous syntax in the Node test suite, even though stealing part of the NPM namespace is confusing. Signed-off-by: Anders Kaseorg <anders@zulipchat.com>
2019-06-21 01:59:21 +02:00
import "../../third/jquery-idle/jquery.idle.js";
third: Upgrade spectrum-colorpicker to 1.8.0 from NPM. We had several patches to spectrum, but the only essential one (0ea770fc180e498ef45ca49dec88f8edd8de868a) had already been fixed upstream, and another was just handling jQuery deprecation warnings for not yet removed features. See #12749 for details. Signed-off-by: Anders Kaseorg <anders@zulipchat.com>
2019-07-10 19:07:34 +02:00
import "spectrum-colorpicker";
webpack: Remove resolve.modules override. The minimal syntactic sugar it might provide isn’t worth the unexpected side effects (including side effects on third party modules). For now, we allow zrequire to emulate the previous syntax in the Node test suite, even though stealing part of the NPM namespace is confusing. Signed-off-by: Anders Kaseorg <anders@zulipchat.com>
2019-06-21 01:59:21 +02:00
import "../../third/marked/lib/marked.js";
webpack: Elide node_modules when importing JS modules. Signed-off-by: Anders Kaseorg <anders@zulipchat.com>
2019-06-21 03:16:48 +02:00
import "xdate/src/xdate.js";
import "jquery-validation/dist/jquery.validate.js";
import "blueimp-md5/js/md5.js";
import "clipboard/dist/clipboard.js";
import "winchan/winchan.js";
webpack: Use handlebars-loader to handle frontend templates. And remove the compile-handlebars-templates system.
2019-06-25 11:39:03 +02:00
import "handlebars/dist/cjs/handlebars.runtime.js";
webpack: Elide node_modules when importing JS modules. Signed-off-by: Anders Kaseorg <anders@zulipchat.com>
2019-06-21 03:16:48 +02:00
import "flatpickr/dist/flatpickr.js";
import "flatpickr/dist/plugins/confirmDate/confirmDate.js";
import "sortablejs/Sortable.js";
webpack: Transition app.js to be compiled by webpack. This commit moves all files previously under the 'app' bundle in the Django pipeline to being compiled by webpack under the 'app' entry point. In the process, it moves assets under the app entry to a file called app.js that consumes all relevant css and js files. This commit also edits the webpack config to be able to expose certain variables for third party libraries that are currently required by some modules. This is bad coding form and should be refactored to requiring whatever dependencies a module may have; we're just deferring that to the future to simplify the series of transitions we need to do here. The variable exposure is done using expose-loader in webpack. The app/index.html template is edited to override the newly introduced 'commonjs' block in the base template. This is done as a temporary measure so as not to disrupt other pages on the app during the transition. It also fixes the value of the 'this' context that was being inferred as window by third party libraries. This is done using imports-loader in the webpack config. This is also messy and probably isn't how we want things to work long term.
2018-05-28 08:09:49 +02:00
// Import App JS
webpack: Remove resolve.modules override. The minimal syntactic sugar it might provide isn’t worth the unexpected side effects (including side effects on third party modules). For now, we allow zrequire to emulate the previous syntax in the Node test suite, even though stealing part of the NPM namespace is confusing. Signed-off-by: Anders Kaseorg <anders@zulipchat.com>
2019-06-21 01:59:21 +02:00
import "../translations.js";
import "../feature_flags.js";
import "../loading.js";
import "../schema.js";
pm_list: Simplify redraws for Private Messages. We now use vdom-ish techniques to track the list items for the pm list. When we go to update the list, we only re-render nodes whose data has changed, with two exceptions: - Obviously, the first time we do a full render. - If the keys for the items have changed (i.e. a new node has come in or the order has changed), we just re-render the whole list. If the keys are the same since the last re-render, we only re-render individual items if their data has changed. Most of the new code is in these two modules: - pm_list_dom.js - vdom.js We remove all of the code in pm_list.js that is related to updating DOM with unread counts. For presence updates, we are now *never* re-rendering the whole list, since presence updates only change individual line items and don't affect the keys. Instead, we just update any changed elements in place. The main thing that makes this all work is the `update` method in `vdom`, which is totally generic and essentially does a few simple jobs: - detect if keys are different - just render the whole ul as needed - for items that change, do the appropriate jQuery to update the item in place Note that this code seems to play nice with simplebar. Also, this code continues to use templates to render the individual list items. FWIW this code isn't radically different than list_render, but it's got some key differences: - There are fewer bells and whistles in this code. Some of the stuff that list_render does is overkill for the PM list. - This code detects data changes. Note that the vdom scheme is agnostic about templates; it simply requires the child nodes to provide a render method. (This is similar to list_render, which is also technically agnostic about rendering, but which also does use templates in most cases.) These fixes are somewhat related to #13605, but we haven't gotten a solid repro on that issue, and the scrolling issues there may be orthogonal to the redraws. But having fewer moving parts here should help, and we won't get the rug pulled out from under us on every presence update. There are two possible extensions to this that are somewhat overlapping in nature, but can be done one a time. * We can do a deeper vdom approach here that gets us away from templates, and just have nodes write to an AST. I have this on another branch, but it might be overkill. * We can avoid some redraws by detecting where keys are moving up and down. I'm not completely sure we need it for the PM list. If this gets merged, we may want to try similar things for the stream list, which also does a fairly complicated mixture of big-hammer re-renders and surgical updates-in-place (with custom code). BTW we have 100% line coverage for vdom.js.
2020-01-04 17:17:44 +01:00
import "../vdom.js";
webpack: Remove resolve.modules override. The minimal syntactic sugar it might provide isn’t worth the unexpected side effects (including side effects on third party modules). For now, we allow zrequire to emulate the previous syntax in the Node test suite, even though stealing part of the NPM namespace is confusing. Signed-off-by: Anders Kaseorg <anders@zulipchat.com>
2019-06-21 01:59:21 +02:00
import "../search_util.js";
import "../keydown_util.js";
import "../lightbox_canvas.js";
import "../rtl.js";
streams: Add LazySet for subscribers. This defers O(N*S) operations, where N = number of streams S = number of subscribers per stream In many cases we never do an O(N) operation on a stream. Exceptions include: - checking stream links from the compose box - editing a stream - adding members to a newly added stream An operation that used to be O(N)--computing the number of subscribers--is now O(1), and we don't even pay O(N) on a one-time basis to compute it (not counting the cost to build the array from JSON, but we have to do that).
2019-12-27 13:16:22 +01:00
import "../lazy_set.js";
webpack: Remove resolve.modules override. The minimal syntactic sugar it might provide isn’t worth the unexpected side effects (including side effects on third party modules). For now, we allow zrequire to emulate the previous syntax in the Node test suite, even though stealing part of the NPM namespace is confusing. Signed-off-by: Anders Kaseorg <anders@zulipchat.com>
2019-06-21 01:59:21 +02:00
import "../dict.ts";
js: Add IntDict class. We don't use this yet, but we will soon. We report errors if users pass in strings instead of ints, but we try to still use the key.
2019-12-29 14:40:02 +01:00
import "../int_dict.ts";
js: Extract FoldDict class. We have ~5 years of proof that we'll probably never extend Dict with more options. Breaking the classes into makes both a little faster (no options to check), and we remove some options in FoldDict that are never used (from/from_array). A possible next step is to fine-tune the Dict to use Map internally. Note that the TypeScript types for FoldDict are now more specific (requiring string keys). Of course, this isn't really enforced until we convert other modules to TS.
2019-12-26 15:34:17 +01:00
import "../fold_dict.ts";
webpack: Remove resolve.modules override. The minimal syntactic sugar it might provide isn’t worth the unexpected side effects (including side effects on third party modules). For now, we allow zrequire to emulate the previous syntax in the Node test suite, even though stealing part of the NPM namespace is confusing. Signed-off-by: Anders Kaseorg <anders@zulipchat.com>
2019-06-21 01:59:21 +02:00
import "../scroll_util.js";
import "../components.js";
import "../feedback_widget.js";
import "../localstorage.js";
import "../drafts.js";
import "../input_pill.js";
import "../user_pill.js";
import "../compose_pm_pill.js";
import "../channel.js";
import "../setup.js";
import "../unread_ui.js";
import "../unread_ops.js";
import "../muting.js";
import "../muting_ui.js";
import "../message_viewport.js";
import "../rows.js";
import "../people.js";
import "../user_groups.js";
import "../unread.js";
topic list: Extract topic_list_data.js. This is mostly for tactical reasons. It's hard to get 100% test coverage on topic_list.js, but it should be easy to get 100% test coverage on this very important function. I considered just moving this code into topic_data.js, but it just didn't feel quite right. I feel like this is a pretty core piece of code that's nice to be by itself and not be near other complicated code that does stuff like build widgets or talk to servers. (And, again, it's not just the actual code here, which is pretty small, it's the unit tests, which are inherently verbose to exercise all the edge cases.)
2020-01-18 13:53:12 +01:00
import "../topic_list_data.js";
webpack: Remove resolve.modules override. The minimal syntactic sugar it might provide isn’t worth the unexpected side effects (including side effects on third party modules). For now, we allow zrequire to emulate the previous syntax in the Node test suite, even though stealing part of the NPM namespace is confusing. Signed-off-by: Anders Kaseorg <anders@zulipchat.com>
2019-06-21 01:59:21 +02:00
import "../topic_list.js";
pm_list: Simplify redraws for Private Messages. We now use vdom-ish techniques to track the list items for the pm list. When we go to update the list, we only re-render nodes whose data has changed, with two exceptions: - Obviously, the first time we do a full render. - If the keys for the items have changed (i.e. a new node has come in or the order has changed), we just re-render the whole list. If the keys are the same since the last re-render, we only re-render individual items if their data has changed. Most of the new code is in these two modules: - pm_list_dom.js - vdom.js We remove all of the code in pm_list.js that is related to updating DOM with unread counts. For presence updates, we are now *never* re-rendering the whole list, since presence updates only change individual line items and don't affect the keys. Instead, we just update any changed elements in place. The main thing that makes this all work is the `update` method in `vdom`, which is totally generic and essentially does a few simple jobs: - detect if keys are different - just render the whole ul as needed - for items that change, do the appropriate jQuery to update the item in place Note that this code seems to play nice with simplebar. Also, this code continues to use templates to render the individual list items. FWIW this code isn't radically different than list_render, but it's got some key differences: - There are fewer bells and whistles in this code. Some of the stuff that list_render does is overkill for the PM list. - This code detects data changes. Note that the vdom scheme is agnostic about templates; it simply requires the child nodes to provide a render method. (This is similar to list_render, which is also technically agnostic about rendering, but which also does use templates in most cases.) These fixes are somewhat related to #13605, but we haven't gotten a solid repro on that issue, and the scrolling issues there may be orthogonal to the redraws. But having fewer moving parts here should help, and we won't get the rug pulled out from under us on every presence update. There are two possible extensions to this that are somewhat overlapping in nature, but can be done one a time. * We can do a deeper vdom approach here that gets us away from templates, and just have nodes write to an AST. I have this on another branch, but it might be overkill. * We can avoid some redraws by detecting where keys are moving up and down. I'm not completely sure we need it for the PM list. If this gets merged, we may want to try similar things for the stream list, which also does a fairly complicated mixture of big-hammer re-renders and surgical updates-in-place (with custom code). BTW we have 100% line coverage for vdom.js.
2020-01-04 17:17:44 +01:00
import "../pm_list_dom.js";
webpack: Remove resolve.modules override. The minimal syntactic sugar it might provide isn’t worth the unexpected side effects (including side effects on third party modules). For now, we allow zrequire to emulate the previous syntax in the Node test suite, even though stealing part of the NPM namespace is confusing. Signed-off-by: Anders Kaseorg <anders@zulipchat.com>
2019-06-21 01:59:21 +02:00
import "../pm_list.js";
import "../pm_conversations.js";
import "../recent_senders.js";
import "../stream_sort.js";
import "../topic_generator.js";
import "../top_left_corner.js";
import "../stream_list.js";
import "../topic_zoom.js";
import "../filter.js";
import "../poll_widget.js";
import "../todo_widget.js";
import "../tictactoe_widget.js";
import "../zform.js";
import "../widgetize.js";
import "../submessage.js";
import "../fetch_status.js";
import "../message_list_data.js";
import "../message_list_view.js";
import "../message_list.js";
import "../message_live_update.js";
import "../narrow_state.js";
import "../narrow.js";
import "../reload_state.js";
import "../reload.js";
import "../compose_fade.js";
import "../fenced_code.js";
import "../markdown.js";
import "../local_message.js";
import "../echo.js";
import "../sent_messages.js";
import "../compose_state.js";
import "../compose_actions.js";
import "../transmit.js";
import "../zcommand.js";
import "../compose.js";
import "../upload.js";
import "../color_data.js";
import "../stream_color.js";
import "../stream_data.js";
import "../topic_data.js";
import "../stream_muting.js";
import "../stream_events.js";
import "../stream_create.js";
import "../stream_edit.js";
import "../subs.js";
import "../message_edit.js";
import "../condense.js";
import "../resize.js";
import "../list_render.js";
import "../floating_recipient_bar.js";
import "../lightbox.js";
import "../ui_report.js";
import "../message_scroll.js";
import "../info_overlay.js";
import "../ui.js";
import "../night_mode.js";
import "../ui_util.js";
import "../pointer.js";
import "../click_handlers.js";
import "../settings_panel_menu.js";
import "../settings_toggle.js";
import "../scroll_bar.js";
import "../gear_menu.js";
import "../copy_and_paste.js";
import "../stream_popover.js";
import "../popovers.js";
import "../overlays.js";
import "../typeahead_helper.js";
import "../search_suggestion.js";
import "../search.js";
import "../composebox_typeahead.js";
import "../navigate.js";
import "../list_util.js";
import "../hotkey.js";
import "../favicon.js";
import "../notifications.js";
import "../hash_util.js";
import "../hashchange.js";
import "../invite.js";
import "../message_flags.js";
import "../starred_messages.js";
import "../alert_words.js";
import "../alert_words_ui.js";
import "../attachments_ui.js";
import "../message_store.js";
import "../message_util.js";
import "../message_events.js";
import "../message_fetch.js";
import "../server_events.js";
import "../server_events_dispatch.js";
import "../zulip.js";
import "../presence.js";
import "../user_search.js";
import "../user_status.js";
import "../user_status_ui.js";
import "../buddy_data.js";
import "../padded_widget.js";
import "../buddy_list.js";
import "../list_cursor.js";
import "../activity.js";
import "../user_events.js";
import "../colorspace.js";
import "../timerender.js";
import "../tutorial.js";
import "../hotspots.js";
import "../templates.js";
import "../upload_widget.js";
import "../avatar.js";
import "../realm_icon.js";
import "../realm_logo.js";
import "../reminder.js";
import "../confirm_dialog.js";
import "../settings_account.js";
import "../settings_display.js";
import "../settings_notifications.js";
import "../settings_bots.js";
import "../settings_muting.js";
import "../settings_sections.js";
import "../settings_emoji.js";
data export: Add UI to trigger data export. This commit serves as the frontend piece for the "public export" webapp feature. Fixes: #11930
2019-04-09 21:49:07 +02:00
import "../settings_exports.js";
webpack: Remove resolve.modules override. The minimal syntactic sugar it might provide isn’t worth the unexpected side effects (including side effects on third party modules). For now, we allow zrequire to emulate the previous syntax in the Node test suite, even though stealing part of the NPM namespace is confusing. Signed-off-by: Anders Kaseorg <anders@zulipchat.com>
2019-06-21 01:59:21 +02:00
import "../settings_org.js";
import "../settings_users.js";
import "../settings_streams.js";
import "../settings_linkifiers.js";
import "../settings_invites.js";
import "../settings_user_groups.js";
import "../settings_profile_fields.js";
import "../settings.js";
import "../admin.js";
import "../tab_bar.js";
import "../emoji.js";
import "../bot_data.js";
import "../reactions.js";
import "../typing.js";
import "../typing_data.js";
import "../typing_events.js";
import "../ui_init.js";
import "../emoji_picker.js";
import "../compose_ui.js";
import "../panels.js";
import "../settings_ui.js";
import "../search_pill.js";
import "../search_pill_widget.js";
import "../stream_ui_updates.js";
webpack: Transition app.js to be compiled by webpack. This commit moves all files previously under the 'app' bundle in the Django pipeline to being compiled by webpack under the 'app' entry point. In the process, it moves assets under the app entry to a file called app.js that consumes all relevant css and js files. This commit also edits the webpack config to be able to expose certain variables for third party libraries that are currently required by some modules. This is bad coding form and should be refactored to requiring whatever dependencies a module may have; we're just deferring that to the future to simplify the series of transitions we need to do here. The variable exposure is done using expose-loader in webpack. The app/index.html template is edited to override the newly introduced 'commonjs' block in the base template. This is done as a temporary measure so as not to disrupt other pages on the app during the transition. It also fixes the value of the 'this' context that was being inferred as window by third party libraries. This is done using imports-loader in the webpack config. This is also messy and probably isn't how we want things to work long term.
2018-05-28 08:09:49 +02:00
// Import Styles
webpack: Remove resolve.modules override. The minimal syntactic sugar it might provide isn’t worth the unexpected side effects (including side effects on third party modules). For now, we allow zrequire to emulate the previous syntax in the Node test suite, even though stealing part of the NPM namespace is confusing. Signed-off-by: Anders Kaseorg <anders@zulipchat.com>
2019-06-21 01:59:21 +02:00
import "../../third/bootstrap-notify/css/bootstrap-notify.css";
third: Upgrade spectrum-colorpicker to 1.8.0 from NPM. We had several patches to spectrum, but the only essential one (0ea770fc180e498ef45ca49dec88f8edd8de868a) had already been fixed upstream, and another was just handling jQuery deprecation warnings for not yet removed features. See #12749 for details. Signed-off-by: Anders Kaseorg <anders@zulipchat.com>
2019-07-10 19:07:34 +02:00
import "spectrum-colorpicker/spectrum.css";
webpack: Elide node_modules when importing JS modules. Signed-off-by: Anders Kaseorg <anders@zulipchat.com>
2019-06-21 03:16:48 +02:00
import "katex/dist/katex.css";
import "flatpickr/dist/flatpickr.css";
import "flatpickr/dist/plugins/confirmDate/confirmDate.css";
webpack: Remove resolve.modules override. The minimal syntactic sugar it might provide isn’t worth the unexpected side effects (including side effects on third party modules). For now, we allow zrequire to emulate the previous syntax in the Node test suite, even though stealing part of the NPM namespace is confusing. Signed-off-by: Anders Kaseorg <anders@zulipchat.com>
2019-06-21 01:59:21 +02:00
import "../../styles/components.scss";
import "../../styles/app_components.scss";
css: Extract rendered_markdown.scss. This moves our main CSS for rendered Zulip message content into an external file, which may be reusable but in any case should make it easier to find this content.
2019-07-31 20:37:06 +02:00
import "../../styles/rendered_markdown.scss";
webpack: Remove resolve.modules override. The minimal syntactic sugar it might provide isn’t worth the unexpected side effects (including side effects on third party modules). For now, we allow zrequire to emulate the previous syntax in the Node test suite, even though stealing part of the NPM namespace is confusing. Signed-off-by: Anders Kaseorg <anders@zulipchat.com>
2019-06-21 01:59:21 +02:00
import "../../styles/zulip.scss";
import "../../styles/alerts.scss";
import "../../styles/settings.scss";
import "../../styles/subscriptions.scss";
import "../../styles/drafts.scss";
import "../../styles/input_pill.scss";
import "../../styles/informational-overlays.scss";
import "../../styles/compose.scss";
import "../../styles/reactions.scss";
import "../../styles/user_circles.scss";
import "../../styles/left-sidebar.scss";
import "../../styles/right-sidebar.scss";
import "../../styles/lightbox.scss";
import "../../styles/popovers.scss";
import "../../styles/typing_notifications.scss";
import "../../styles/hotspots.scss";
import "../../styles/night_mode.scss";
import "../../styles/user_status.scss";
import "../../styles/widgets.scss";
templates: Make the Loading… message more robust. Don’t hide it until both CSS and JS have loaded. Signed-off-by: Anders Kaseorg <anders@zulipchat.com>
2019-09-20 06:43:04 +02:00
// This should be last.
import "../ready.js";