| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
| |
Signed-off-by: John Molakvoæ (skjnldsv) <skjnldsv@protonmail.com>
|
|\
| |
| | |
Disable failing test in legacy sharing tests
|
| |
| |
| |
| |
| |
| | |
* seems to be a race condition
Signed-off-by: Morris Jobke <hey@morrisjobke.de>
|
|/ |
|
| |
|
|\
| |
| | |
Feature/shares overview
|
| |
| |
| |
| | |
Signed-off-by: John Molakvoæ (skjnldsv) <skjnldsv@protonmail.com>
|
| |
| |
| |
| | |
Signed-off-by: Morris Jobke <hey@morrisjobke.de>
|
| |
| |
| |
| | |
Signed-off-by: Morris Jobke <hey@morrisjobke.de>
|
| |
| |
| |
| | |
Signed-off-by: Morris Jobke <hey@morrisjobke.de>
|
| |
| |
| |
| | |
Signed-off-by: John Molakvoæ (skjnldsv) <skjnldsv@protonmail.com>
|
| |
| |
| |
| |
| |
| |
| |
| | |
Signed-off-by: John Molakvoæ (skjnldsv) <skjnldsv@protonmail.com>
Fixed if condition
Signed-off-by: John Molakvoæ (skjnldsv) <skjnldsv@protonmail.com>
|
| |
| |
| |
| | |
Signed-off-by: John Molakvoæ (skjnldsv) <skjnldsv@protonmail.com>
|
| |
| |
| |
| | |
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
|
| | |
|
| | |
|
|\ \
| | |
| | | |
sharedWithDisplayName & sharedWithAvatar
|
| | |
| | |
| | |
| | |
| | | |
Signed-off-by: Maxence Lange <maxence@nextcloud.com>
Signed-off-by: Morris Jobke <hey@morrisjobke.de>
|
|\ \ \
| |_|/
|/| |
| | |
| | | |
nextcloud/fix-formatting-of-email-and-circle-shares
Fix formatting of email and circle shares
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Due to a misplaced "||" instead of "===" the condition was always met,
so every share type in the conditional chain after the remote and remote
group shares was formatted as a remote/remote group share.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
|
|/ / |
|
|\ \
| | |
| | | |
implement federated group sharing
|
| | |
| | |
| | |
| | | |
Signed-off-by: Bjoern Schiessle <bjoern@schiessle.org>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Bjoern Schiessle <bjoern@schiessle.org>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Bjoern Schiessle <bjoern@schiessle.org>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Bjoern Schiessle <bjoern@schiessle.org>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Bjoern Schiessle <bjoern@schiessle.org>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Bjoern Schiessle <bjoern@schiessle.org>
|
|/ / |
|
| | |
|
| |
| |
| |
| | |
Signed-off-by: John Molakvoæ (skjnldsv) <skjnldsv@protonmail.com>
|
| |
| |
| |
| | |
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
|
| |
| |
| |
| | |
Signed-off-by: John Molakvoæ (skjnldsv) <skjnldsv@protonmail.com>
|
| |
| |
| |
| | |
Signed-off-by: John Molakvoæ (skjnldsv) <skjnldsv@protonmail.com>
|
| |
| |
| |
| | |
Signed-off-by: John Molakvoæ (skjnldsv) <skjnldsv@protonmail.com>
|
| |
| |
| |
| | |
Signed-off-by: John Molakvoæ (skjnldsv) <skjnldsv@protonmail.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When a group share is deleted we keep track of this in the DB.
Right now it is only possible for a recipient to get back the share by
asking the sharer to delete it and to share it again. This doesn't
scale.
This endpoint makes it possible to get back the share.
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
|
| |
| |
| |
| | |
Signed-off-by: Bjoern Schiessle <bjoern@schiessle.org>
|
| |
| |
| |
| | |
Signed-off-by: Bjoern Schiessle <bjoern@schiessle.org>
|
| |
| |
| |
| | |
Signed-off-by: Bjoern Schiessle <bjoern@schiessle.org>
|
| |
| |
| |
| | |
Signed-off-by: Bjoern Schiessle <bjoern@schiessle.org>
|
| |
| |
| |
| | |
Signed-off-by: Bjoern Schiessle <bjoern@schiessle.org>
|
|\ \
| | |
| | |
| | |
| | | |
nextcloud/fix-getting-the-information-of-a-group-share-as-a-sharee
Fix getting the information of a group share as a sharee
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When the receiver of a group share modifies it (for example, by moving
it to a different folder) the original share is not modified, but a
"ghost" share that keeps track of the changes made by that specific user
is used instead.
By default, the method "getShareById" in the share provider returns the
share from the point of view of the sharer, but it can be used too to
get the share from the point of view of a sharee by providing the
"recipient" parameter (and if the sharee is not found then the share is
returned from the point of view of the sharer).
The "ShareAPIController" always formats the share from the point of view
of the current user, but when getting the information of a specific
share the "recipient" parameter was not given, so it was always returned
from the point of view of the sharer, even if the current user was a
sharee. Now the "recipient" parameter is set to the current user, and
thus the information of the share is returned from the point of view of
the current user, be it the sharer or a sharee.
Note that this special behaviour of "getShareById" happens only with
group shares; with other types of shares the share is the same for the
sharer and the sharee, and thus the parameter is ignored; it was added
for them too just for consistency.
Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
|
|\ \ \
| |/ /
|/| | |
Get rid of shareItem
|
| | |
| | |
| | |
| | |
| | |
| | | |
so no need to fix the tests
Signed-off-by: Roeland Jago Douma <roeland@famdouma.nl>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Morris Jobke <hey@morrisjobke.de>
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
nextcloud/techdebt/noid/replace-headers-with-http_response_code-calls
Replace hard coded HTTP status codes with proper calls to http_response_code
|