Clears up some naming confusion - `REALM_CREATION_LINK_VALIDITY_DAYS` is
a setting which describes the validaty period of RealmCreationKey, not
of Confirmation with REALM_CREATION type. Now that the latter is called
NEW_REALM_USER_REGISTRATION, there should be no confusion about this.
This commit refactors to import the full
`left_sidebar_navigation_area` module instead of
individual functions. This allows calling multiple
functions easily and prepares for upcoming navigation
view changes.
This commit adds 'highlighted-element' class to <b> tags in
the following onboarding modals:
* introduce inbox view modal
* introduce recent conversations view modal
* introduce resolve topic modal
* introduce first channel created modal
'highlighted-element' class sets the 'font-weight: 600',
replacing the default of 700.
We remove the ol > li margin rule to space out ordered list items since
that was the result of us overriding an upstream margin rule in
steps.css.
We inserted Steps inside include files only if they are not entirely
composed of an ordered list. If they are, they will eventually be
wrapped inside FlattenedSteps and wrapping these macros with Steps will
not give us the results we desire.
Using steps.css right now might feel like the more convenient way out,
but it might introduce friction in upgrades when the upstream code
changes. To tackle that, we convert FlattenList to FlattenedSteps and
explicitly use the steps component.
This commit refactors code for DropdownWidget to handle clicks
on edit and delete buttons in a separate click event handler
and not in the handler for selecting one of the items in
dropdown.
This is important to make sure that selected value stored for
dropdown widget is not updated on clicking the icon.
This commit updates code to require unique names for only
non-archived folders in a realm, which means a folder can
use a name which is being used by an archived folder.
This commit adds live-update code to reset the dropdown when user
is changing the folder for a channel or setting the folder for a
new channel and the selected folder is archived.
This commit updates code to pass aria-label for icon buttons
in dropdown widget options so that they can be used in
dropdown_list.hbs template instead of directly defining them
in the template file.
We currently show buttons in saved snippets dropdown only
so defining the labels in template file worked correctly
but it is good to pass them as variables so that it is
simpler to add buttons for other dropdowns when required.
The order of token values returned by the database query isn't
guaranteed, so 'assertEqual' fails in a flaky way.
This commit uses 'assertCountEqual' to fix that.
The `update_desktop_notification_banner` line removed had been added in #34865,
to handle the case of opening the default user settings panel after previously opening
the personal; notifications settings panel, and is no longer required.
Previously, only one bot can be created using the
generate-integration-docs-screenshot script for each integration. This
was because the bot's email was constructed using the integration's
name.
Thus, the bot-name commandline option would not work if a bot already
exists for the integration.
Now, we create the email by cleaning the bot-name value, if passed.
The format step was converting our ordered list items to have
incremental numbering instead of using `1.` for every list item. This
was not because of any remark-lint rule, but because of
`remark-stringify` which auto increments any lists it processes. We
followed the recommended fix from
ae2f941d88/packages/remark-lint-ordered-list-marker-value/readme.md (L185)
We also don't need remark-lint-ordered-list-marker-value package, since
that is already part of the markdown style guide with the value we
desire. Setting it to false was a mistake in the first place.
Use the icon's name, in camelcase, with the suffix "Icon" for
icon class names in the new help center documentation. E.g.,
zulip-icon-external-link becomes ExternalLinkIcon and fa fa-plus
becomes PlusIcon.
This commit updates the organization settings banners to use
`width: fit-content`, ensuring they no longer span the full available
width. While this change does not yet support wrapping the action button
to a new line, it works reliably for these banners.
Currently, flex-wrap is set to `nowrap` to prevent buttons from wrapping
to the next line, as using `min-content` or `fit-content` forces
wrapping when space runs out. This approach limits the banner width to
its content size while maintaining layout consistency.
Making this as a separate commit since this is an experimental change
and we can tinker this later when we have a solid solution.
This commit redesigns the upgrade and sponsorship banners by adding
AVAILABLE_ON_STANDARD, UPGRADE_ACCESS_BANNER, and
UPGRADE_OR_SPONSORSHIP_BANNER.
Fixes part of #34252.
This commits convert the banners of "Settings > Default user settings"
and "Personal > Bots" into plain text. Also, change the plain text of
"Personal > Bots" to be more descriptive.
Fixes part of #34252.
In the help center, we want these two system bots to be referred
to as names: capitalize both words, no bold, no links, no "the"
before the bot's name.
Currently, we save a draft copy in case message send fails on server
but this only saves a copy of message when it has savable message
length. Short message doesn't save a copy and throws an error.
This commit introduces a new option `force_save` to `update_draft`
and saves any message regardless of message length if passed true.
