Updated the fixtures as OpenSearch sends text payloads in the template
given by the user.
Updated the doc to suggest using global time in the example template.
Fixes: #36570.
Modify `sort_bot_owner` to place bots without an owner at the bottom
when sorting by the "Owner" column. This groups bots with owners
together for easier scanning.
The logic first prioritizes moving any bot with "No owner" to the
bottom of the list. Alphabetical name comparison is only applied when
both bots have owners to compare.
This commit removes transition for background-color on hovering over
table headers with "data-sort" attribute.
This is done so that we can fix the weird behavior of background
color of header being set to a weird value when clicking on a
dropdown widget option rendered over the table header for bots table.
This was likely due to transition being stopped midway by the browser
which resulted in a weird background highlight for the header.
And anyways the transition is brief and appears only on hover, so
removing it does not result in a major change of user behavior.
The user_group module must be initialized before people
module, so that can_access_all_users_group setting group
can be used to check whether the user has permission to
access all other users.
Zulip production suite / ${{ matrix.name }} (zulip/ci:bookworm, --test-custom-db, Debian 12 production install with custom db name and user, bookworm) (push) Has been cancelled
Zulip production suite / ${{ matrix.name }} (zulip/ci:jammy, , Ubuntu 22.04 production install and PostgreSQL upgrade with pgroonga, jammy) (push) Has been cancelled
This commit adds a unified keydown listener to both the task name (`input.add-task`)
and description (`input.add-desc`) input elements. Pressing Enter triggers the `add_task()`
function, enabling keyboard-based submission of new tasks in the widget.
Previously, we maintained separate registeries for the screenshot
configurations - `WEBHOOK_SCREENSHOT_CONFIG`,
`FIXTURELESS_SCREENSHOT_CONFIG`, `DOC_SCREENSHOT_CONFIG`. Now, all
integration-related configuration is in a single registry
`INTEGRATIONS`.
Updated all mentions of DOC_SCREENSHOT_CONFIG in the docs.
We still have to check whether we have a valid lang value or not since
markdown.ts does not pass a lang, and depends on this logic to continue
working the same as before.
This adds two new options to the left sidebar filter menu:
- Expand all sections (zulip-icon-expand)
- Collapse all sections (zulip-icon-collapse)
These appear above the existing "Don't group channels by folder" entry,
and expand/collapse all sidebar sections (Views, DMs, folders, etc.)
at once.
Fixes#35884.
We add a acting_user to get relevant permissions to render the
reminder message. This in turn fixes channel links not rendering
properly when notification bot is not in private channel.
Fixes: zulip#36575.
We now wrap single liner code content in a language block if the
required metadata is present in the `paste_html`. The inline
markdown paste behavior now only applies to codeblocks that don't
have a language associated with them or miss the language
metatdata in the `paste_html`.
The latter will occur less frequently after change
that will be introduced in the following commit.
Signed-off-by: apoorvapendse <apoorvavpendse@gmail.com>
Also, restore scroll position when input is cleared.
Tested locally that the scroll position is properly restored
in left sidebar search, topic zoom and DM zoom states.
All this bunch of logic for processing the configuration and generating
the sets of syncable+intended groups is fairly long and makes the core
social_auth_sync_user_attributes logic very hard to read.
This clearly belongs in a helper function.
This commit adds code to show a "Download zuliprc" button
for "Generic" bots and "Generate URL for integration" button
for "Incoming Webhook" bots in "Actions" column of the bots
table as they are commonly used actions and would be good
to have it such that they are easy to access.
URL integration button is shown to admins and bot owners and
download zuliprc button is only shown to bot owner which is
same as what we do in "Manage bot" form.
