In Nextcloud Vue v8 the `type` prop for dialog buttons
was deprecated and replaces with the `variant` prop.
In v9 the deprecated props are removed.
Use the `variant` prop in the deprecated `OC.dialogs`.
This is a follow up for #55726.
Signed-off-by: Max <max@nextcloud.com>
The supportsActiveFilters variable was used but never defined, causing
the filtered/unfiltered results separation to fail silently.
Signed-off-by: nfebe <fenn25.fn@gmail.com>
Show results from providers that don't support active content filters
(date/person) in a separate "Additional results" section with a note
explaining that some filters may have been ignored.
Changes:
- Add computed properties to separate filtered/unfiltered results
- Track filter compatibility using baseProvider for searchFrom providers
- Deduplicate results by resourceUrl across sections
- Skip in-folder results when at root to avoid duplicating Files results
- Fix providerIsCompatibleWithFilters to check correct filter properties
- Add styling for the unfiltered results section
Signed-off-by: nfebe <fenn25.fn@gmail.com>
When date range or person filters were applied, providers that didn't
support these filters were automatically disabled in the UI. This made
the in-folder filter appear auto-applied and prevented users from
searching non-compatible providers.
Remove automatic provider disabling logic from updateDateFilter(),
applyPersonFilter(), and removeFilter(). Content filters now apply only
to compatible providers via existing compatibility checks while keeping
all providers available for selection.
Signed-off-by: nfebe <fenn25.fn@gmail.com>
After ec9e283e there was still such a problem with the legacy app navigation
snapper that its width was only 266 px on the RTL layout instead of the
normal 300 px. The 266 px is the default width of Snap.js module. While the
left side snapper width is configured with the property maxPosition, the right
side snapper is configured by passing a negative value for the property
minPosition.
Signed-off-by: Pauli Järvinen <pauli.jarvinen@gmail.com>
Signed-off-by: nextcloud-command <nextcloud-command@users.noreply.github.com>
With SSO setups users may otherwise be redirected to the IdP directly
instead of the regular login form that they reset the password for
Signed-off-by: Julius Knorr <jus@bitgrid.net>
This setting existed already for the legacy unified search.
This commit expose that setting to the new front-end, and
also ignore non valid requests in the backend.
We also take the opportunity to register the config in the lexicon.
Signed-off-by: Louis Chemineau <louis@chmn.me>
Couple of versions ago:
- `color-text-light` was replaced with `color-main-text`
- `color-text-lighter` was replaced with `color-text-maxcontrast`
Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
This removes:
- “enable” for settings
- “settings” for settings sections
- “all” when there is no obvious subset of items
- “show” and “open” for navigation actions
- “changes” for applying/discarding
- “to clipboard” when copying
- Explaining things that cannot happen
- Explaining things twice, right below each other
- Unnecessary technical jargon
- Text that sounds like marketing copy and serves no other purpose
Signed-off-by: kramo <git@kramo.page>
This commit introduces a change to prevent showing the load more button,
if the length of existing results is not equal to the requested limit (which implies
it is less than because we never expect it to be more)
Additionally, there is an enhancment to override provider filders passed to the find method.
This would improve speed.
Signed-off-by: nfebe <fenn25.fn@gmail.com>
We hide **if** there is **no** notification.
We *do not* hide and *show the label* **if** there are notifications for
that application.
Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
app icons in the header navigation are excluded from the outlined icons
change, so this reverts this change.
Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
The unified search modal was intended to be cleared when closed.
However, "UnifiedSearchModal" did not emit "update:query" when its
internal query value ("searchQuery") changed, so "UnifiedSearch.query"
was kept as an empty string. When the modal was closed "update:query"
was emitted with an empty string, which should have cleared
"UnifiedSearch.query" and that, in turn, should have cleared the modal.
However as "UnifiedSearch.query" was already an empty string the watcher
that updates "UnifiedSearchModal.searchQuery" from "UnifiedSearch.query"
was not triggered and the modal was not cleared.
As "UnifiedSearch.query" is now updated with the value of
"UnifiedSearchModal.searchQuery" the latter can not be trimmed when
updated from the former, as that would in turn also trim
"UnifiedSearchModal.searchQuery" and prevent to search for anything with
spaces at the beginning or end (even if those trailing spaces are just
temporary while writing something like "searched value").
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
