Uh oh!
There was an error while loading. Please reload this page.
allow to create multiple link shares via share api - #11844
Conversation
cc @AndyScherzinger@tobiasKaminsky@marinofaggiana@camilasan@rullzer With Nextcloud 15 we will support multiple share links. This PR already implements everything you need to start implementing it on the client side. Just in case you are looking for something to do 😉 Creating links works the same as before. There is just the additional parameter "label" you can use to create/update link shares so that the user can give the share link names to remember which link was used for what. |
marinofaggiana
commented
Oct 18, 2018
ToDo added :-) |
jancborchardt
commented
Oct 18, 2018
I’d suggest to split this up to prevent it from becoming too big of a pull request: API stuff:
Basic interface stuff:
Future interface stuff that is optional:
Especially since you already mentioned the possible conflicts with #11537 (which is quite short so shouldn’t really conflict a lot.) |
fb8bae2 to
18e720dCompare18e720d to
c26d581CompareUh oh!
There was an error while loading. Please reload this page.
Just had a short call with @skjnldsv, and this is the spec now:
That’s that for now. Did I forget anything @skjnldsv? |
Signed-off-by: Bjoern Schiessle <bjoern@schiessle.org>
b7bdd4b to
9503528CompareShould be finished today! Can you start a review now? Basically the only thing left is the label handling! How should we do that?
|
jancborchardt
commented
Oct 31, 2018
Just beginning to test this! :) First feedback:
|
jancborchardt
commented
Oct 31, 2018
Made the background of the share link primary color instead of bland grey. This is in line with the change in the Talk app at nextcloud/spreed#1274 |
skjnldsv
commented
Oct 31, 2018
I was afraid it would be too much, but it is spot on!! 👍 |
danxuliu
left a comment
There was a problem hiding this comment.
Fixed
Not so fast; I have some complaints ;-)
skjnldsv
commented
Nov 1, 2018
@danxuliu be quick! |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
957b150 to
719e977Compare
danxuliu
left a comment
There was a problem hiding this comment.
Fixed :D
Almost :-P I will send a final fix.
skjnldsv
commented
Nov 1, 2018
Failure unrelated: |
skjnldsv
commented
Nov 1, 2018
Ahaha! Okay :) |
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>
Signed-off-by: John Molakvoæ (skjnldsv) <skjnldsv@protonmail.com>
Signed-off-by: Jan-Christoph Borchardt <hey@jancborchardt.net>
Although now it is possible to create several link shares the acceptance tests currently handles only the first link share; this first link share is now created by clicking an "Add new share" button instead of a checkbox. Besides that, the "Copy link" button has been moved from the menu to the row, next to the menu trigger. Signed-off-by: Daniel Calviño Sánchez <danxuliu@gmail.com>
Signed-off-by: Jan-Christoph Borchardt <hey@jancborchardt.net>
Signed-off-by: John Molakvoæ (skjnldsv) <skjnldsv@protonmail.com>
Signed-off-by: John Molakvoæ (skjnldsv) <skjnldsv@protonmail.com>
719e977 to
876d6ecCompare
danxuliu
left a comment
There was a problem hiding this comment.
Rejoice; finally, the nitpicker is reasonably satisfied 👍
I hope Drone is too... :-P
MorrisJobke
commented
Nov 1, 2018
🎉 I will merge once drone has done it's job 🎉 |
876d6ec to
ef7d2a0Compareef7d2a0 to
876d6ecComparelopezio
commented
May 3, 2019
@schiessle@jancborchardt any progress on these points..? I think they're fundamental to make the multiple linking functionality usable.. with some kind of distinction between the shared links it would be possible to explicitely delete or re-share links based on a target public / individual.. Best Regards! |

for ux discussion, etc see #11169
Fix#10434
Closes#11537 : not possible, we cannot wait for the request of a new share to be done as the
.doneorsuccesshooks generate a new scope and a clipboard triggered by a click needs to be in a direct call of a function triggered by an event :(Fix#11169