Mirror
/
zulip
mirror of https://github.com/zulip/zulip.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
zulip/web/templates/settings/bot_list_admin.hbs

44 lines
2.2 KiB
Handlebars
Raw Normal View History

frontend: Make ID assignments unique.
2017-07-11 11:24:51 +02:00
<div id="admin-bot-list" class="settings-section" data-name="bot-list-admin">
bots: Improve bots permission banner. Added a separate template file for banner messages in bots panel under personal and organisation settings. Banners for bots panel under personal settings are shown only when user cannot add bots. Banners for bots panel under organisation settings are shown only when user cannot add bots or user is administrator. Fixes #24155
2023-03-03 14:14:01 +01:00
<div class="bot-settings-tip" id="admin-bot-settings-tip">
</div>
Remove headers from templates.
2017-05-09 22:09:31 +02:00
<div class="clear-float"></div>
settings_bots: Make it possible to add new bots from org settings. Adding an "Add a new bot" button to Organization settings > Bots, which opens a `Add a new bot` form modal from `settings_bots.js`. Fixes #20309.
2022-09-16 12:40:13 +02:00
<div>
settings: Remove "add a new bot button" from admin page. Instead, we show a message with links that either opens a modal for creating a new bot or navigates to the bot settings page. The "add a new bot" link only show up when the user has enough permission to create new bots, and the "manage your bots" link only shows up when the user has at least one bot if they don't have the permission to create one. Otherwise, the message does not show up at all. Signed-off-by: Zixuan James Li <p359101898@gmail.com>
2023-01-24 22:33:40 +01:00
{{t "You are viewing all the bots in this organization." }}
{{#if can_create_new_bots}}
{{#tr}}
You can <z-link-new-bot>add a new bot</z-link-new-bot> or <z-link-manage-bot>manage</z-link-manage-bot> your own bots.
{{#*inline "z-link-new-bot"}}<a class="add-a-new-bot">{{> @partial-block}}</a>{{/inline}}
{{#*inline "z-link-manage-bot"}}<a href="/#settings/your-bots">{{> @partial-block}}</a>{{/inline}}
{{/tr}}
{{else if has_bots}}
{{#tr}}
You can <z-link>manage</z-link> your own bots.
{{#*inline "z-link"}}<a href="/#settings/your-bots">{{> @partial-block}}</a>{{/inline}}
{{/tr}}
{{/if}}
settings_bots: Make it possible to add new bots from org settings. Adding an "Add a new bot" button to Organization settings > Bots, which opens a `Add a new bot` form modal from `settings_bots.js`. Fixes #20309.
2022-09-16 12:40:13 +02:00
</div>
settings: Make list header sections consistent. I made the header sections above all our settings panel lists more consistent. Before this change: * some lists had titles, others didn't * the placement of the filter box was random * alerts strangely went between the filter box and the list * filter boxes were too large * CSS was haphazard * forms were squished against tables Now all the settings with list have consistent HTML, CSS, and look-and-feel in the area directly above their list of items. With the exception of Custom Profile Fields, all the lists with headers above them happen to be based on ListWidget, but the header styling is not coupled to ListWidget, because we want consistent headers even if Custom Profile Fields has a non-ListWidget list (due to its drag&drop features).
2022-03-04 13:06:28 +01:00
<div class="settings_panel_list_header">
<h3>{{t "Bots"}}</h3>
settings: Place the saving indicator in the header. Fixes #21441.
2022-03-20 17:58:28 +01:00
<div class="alert-notification" id="bot-field-status"></div>
templates: Add filter_text_input class to inputs used for filtering. This commit adds filter_text_input class to various search inputs used across the app. This new class is used to re-add the bootstrap CSS rules such that we can remove the CSS from bootstrap.css.
2023-06-23 13:22:29 +02:00
<input type="text" class="search filter_text_input" placeholder="{{t 'Filter bots' }}" aria-label="{{t 'Filter bots' }}"/>
settings: Make list header sections consistent. I made the header sections above all our settings panel lists more consistent. Before this change: * some lists had titles, others didn't * the placement of the filter box was random * alerts strangely went between the filter box and the list * filter boxes were too large * CSS was haphazard * forms were squished against tables Now all the settings with list have consistent HTML, CSS, and look-and-feel in the area directly above their list of items. With the exception of Custom Profile Fields, all the lists with headers above them happen to be based on ListWidget, but the header styling is not coupled to ListWidget, because we want consistent headers even if Custom Profile Fields has a non-ListWidget list (due to its drag&drop features).
2022-03-04 13:06:28 +01:00
</div>
list_render: Remove data-list-render markup. We already know which list widget a `<th>` tag is associated with when we set up the event handler, so it's silly to read data from the DOM to find that widget again when the handler runs. This commit eliminates a whole class of possible errors and busy work.
2020-04-15 12:22:23 +02:00
<div class="progressive-table-wrapper" data-simplebar>
templates: Remove table-condensed class for <table> elements. The table-condensed class was used by bootstrap to add padding to the table cells. But since we want padding in cells for all tables, we added the padding CSS to the other existing CSS for tables while removing the bootstrap CSS for tables and "table-condensed" is not required anymore.
2023-08-07 09:32:19 +02:00
<table class="table table-striped wrapped-table">
settings css: Make HTML table headers sticky. Introduce a new class "table-sticky-headers" in the settings and organisation settings HTML table tags and it is used to make the table headers fix at the top. This commit also add the background-color and hover properties to the settings and organisation settings table to make them look similar to the recent_topics_table.
2021-02-23 06:23:24 +01:00
<thead class="table-sticky-headers">
org settings: Reduce the width occupied by the actions column in tables.
2019-08-22 10:33:44 +02:00
<th class="active" data-sort="alphabetic" data-sort-prop="full_name">{{t "Name" }}</th>
user settings: Fix email sort for bots/deactivateds. We were still sorting them with the generic alphabetic sort due to the markup, despite passing in a custom sort to the `list_render` class. The `sort_email` helper often behaves like a generic alphabetic sort, so this fix is mostly just making the code do what it claims to do (and it's consistent with how we already sort active users). The nuance with emails is whether we display real emails or system-generated emails.
2020-05-10 14:08:54 +02:00
<th data-sort="email">{{t "Email" }}</th>
org_settings: Add "Role" column in bot-list table. This commit adds a new "Role" column for the bot-list table in the org-settings, and removes the user_id column from the same. The role of a bot is fetched using the `get_user_type` function inside bot_info(). This also adds the `sort_role` in the sort_fields which sorts the role column in the bot-list table.
2022-03-31 08:31:45 +02:00
<th class="user_role" data-sort="role">{{t "Role" }}</th>
refactor: Group header and body under table for .progressive-table-wrapper.
2019-08-22 06:23:41 +02:00
<th data-sort="bot_owner">{{t "Owner" }}</th>
settings: Drop column from tables on narrow screen. Drop the "last_active" column in the users section of the organization settings, and the "Bot_type" column in the bots section on sm_min (576px or less). Also, drop the "Date_muted" column in the muted topics section of the personal settings on ml_min (425px or less). Added new className "topic_date_muted" for the date_muted column, and "bot_type" for the bot_type column, to hide them using display none when the viewport is small. Fixes: #24320
2022-10-11 14:20:27 +02:00
<th data-sort="alphabetic" data-sort-prop="bot_type" class="bot_type">{{t "Bot type" }}</th>
refactor: Group header and body under table for .progressive-table-wrapper.
2019-08-22 06:23:41 +02:00
{{#if is_admin}}
<th class="actions">{{t "Actions" }}</th>
{{/if}}
</thead>
Add placeholders to all empty lists. This adds placeholders that state that the lists are empty.
2017-05-12 02:48:53 +02:00
<tbody id="admin_bots_table" class="admin_bot_table required-text thick"
linter: Enforce 2 space indents on tags spread over multiple lines. We make some specific cases of tags use 2 space indents. The case description: * A tag with opening tag spread over multiple lines and closing tag on the same line as of the closing angle bracket of the opening tag. * A tag with opening tag spread over multiple lines and closing tag not on the same line as of the closing angle bracket of the opening tag. Example: Case 1: Not linted: <button type="button" class="btn btn-primary btn-small">{{t "Yes" }}</button> After linting: <button type="button" class="btn btn-primary btn-small">{{t "Yes" }}</button> Case 2: Before linting: <div class = "foo" id = "bar" role = "whatever"> {{ bla }} </div> After linting: <div class = "foo" id = "bar" role = "whatever"> {{ bla }} </div>
2018-04-05 08:38:46 +02:00
data-empty="{{t 'No bots match your current filter.' }}"></tbody>
Change admin bots list to render progressively.
2017-04-20 21:58:12 +02:00
</table>
</div>
<div id="admin_page_bots_loading_indicator"></div>
Separate bot list from admin_tab template. This separates bot list settings into its own template in the templates/settings folder.
2016-10-05 02:49:17 +02:00
</div>