| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|\
| |
| | |
fix: unified search provider id
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The client-side plugin `in-folder` uses the `files` provider, this makes it
overlap with the main files provider itself.
This change follows eecda06f1ad2832cc2a7b31d646458f730c8412a after it was discovered
that some apps/providers like `dav` use providers from another app like `contacts`
Signed-off-by: nfebe <fenn25.fn@gmail.com>
Signed-off-by: nextcloud-command <nextcloud-command@users.noreply.github.com>
|
| |
| |
| |
| |
| | |
Signed-off-by: SebastianKrupinski <krupinskis05@gmail.com>
Signed-off-by: nextcloud-command <nextcloud-command@users.noreply.github.com>
|
|/
|
|
| |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|
|
|
| |
Signed-off-by: provokateurin <kate@provokateurin.de>
|
|
|
|
| |
Signed-off-by: Nils Wenninghoff <nils@ungemein.cool>
|
|
|
|
| |
Signed-off-by: nfebe <fenn25.fn@gmail.com>
|
|
|
|
| |
Signed-off-by: nfebe <fenn25.fn@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Each provider may search from a particular app so we should use that for searching.
Before this commit, we used `provider.id` instead of `provider.appId` the problem with the previous
approach is that it forces the provider id to be a valid search provider (an app that supports search)
limiting the developers ability to use unique IDs to identify the different providers (especially plugin providers)
inside the places filter.
For example the Files search plugin "In folder" (search in folder plugin) was required to have id as `files` while the
files provider itself already has id as `files`.
Signed-off-by: nfebe <fenn25.fn@gmail.com>
|
|
|
|
|
|
|
| |
If `ignore-missing-user` all sub commands work, except listing all settings
for a user like `occ user:settings --ignore-missing-user user core`.
Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
|
|
|
|
|
|
|
| |
Ensure that the if a preview is available the maximum sizes are
respected (clickable area).
Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
|
|
|
|
| |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|
|
|
|
|
| |
in order to hide sensitive data from logs
Signed-off-by: Misha M.-Kupriyanov <kupriyanov@strato.de>
|
|
|
|
| |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|
|
|
| |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|
|
|
| |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|
|
|
| |
Signed-off-by: nextcloud-command <nextcloud-command@users.noreply.github.com>
|
|
|
|
| |
Signed-off-by: skjnldsv <skjnldsv@protonmail.com>
|
|
|
|
| |
Signed-off-by: skjnldsv <skjnldsv@protonmail.com>
|
|
|
|
| |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|
|
|
| |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|\
| |
| | |
feat: Two Factor API
|
| |
| |
| |
| | |
Signed-off-by: SebastianKrupinski <krupinskis05@gmail.com>
|
|\ \ |
|
| | |
| | |
| | |
| | | |
Signed-off-by: Maksim Sukharev <antreesy.web@gmail.com>
|
|/ /
| |
| |
| | |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
| |
| |
| |
| | |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|/
|
|
|
|
|
|
|
|
| |
- Add default value to non-required Vue props
- Reformat function to async function if needed
- Add some documentation
- Allow `any` in places where it makes sense (tests)
- Order vue component sections as required
Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
|
|
|
|
| |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|
|
|
| |
Signed-off-by: skjnldsv <skjnldsv@protonmail.com>
|
|
|
|
| |
Signed-off-by: Maxence Lange <maxence@artificial-owl.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Vue3 does not replace the element while mounting but only renders within
(replace inner HTML).
So it would result in two stacked `<main>` elements which is invalid and
an accessibility issue.
Instead we just use a `<div>` element for mounting.
For Vue2 apps this does not change anything as the whole element will be
replaced with a new `<main>` element.
For vanilla apps this will slightly decrease the accessibility as the
main landmark is now missing, but this is not a hard accessibility issue
as it would be for Vue3 apps having two main elements.
Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
|
|
|
|
| |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|\
| |
| | |
fix: Make `maintenance:mode` description more accurate + add help
|
| |
| |
| | |
Signed-off-by: Josh <josh.t.richards@gmail.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Some filters are only available for certain providers, the UI should give the user
a hint to what providers such filters are available in.
Currently, if a filter (date or person) is not support by an a provider, the provider is
blurred out in the places dropdown.
Signed-off-by: nfebe <fenn25.fn@gmail.com>
|
| |
| |
| |
| | |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
| |
| |
| |
| | |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
| |
| |
| |
| | |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|\ \
| | |
| | | |
fix: Apply enforce theme config for anonymous users as well
|
| | |
| | |
| | |
| | | |
Signed-off-by: Kostiantyn Miakshyn <molodchick@gmail.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Richard Steinmetz <richard@steinmetz.cloud>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Julien Veyssier <julien-nc@posteo.net>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Julien Veyssier <julien-nc@posteo.net>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|/ /
| |
| |
| | |
Signed-off-by: Nextcloud bot <bot@nextcloud.com>
|
|\ \
| | |
| | | |
feat: Add first login timestamp of each user to oc_preferences and user:info output
|
| | |
| | |
| | |
| | |
| | |
| | | |
Also format unknown and never in a better way.
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Côme Chilliet <come.chilliet@nextcloud.com>
|