-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
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. |
ToDo added :-) |
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
18e720d
Compare
18e720d
to
c26d581
Compare
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 <[email protected]>
b7bdd4b
to
9503528
Compare
Should be finished today! Can you start a review now? Basically the only thing left is the label handling! How should we do that?
|
Just beginning to test this! :) First feedback:
|
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 |
I was afraid it would be too much, but it is spot on!! 👍 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed
Not so fast; I have some complaints ;-)
@danxuliu be quick! |
957b150
to
719e977
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed :D
Almost :-P I will send a final fix.
Failure unrelated: |
Ahaha! Okay :) |
Signed-off-by: John Molakvoæ (skjnldsv) <[email protected]>
Signed-off-by: John Molakvoæ (skjnldsv) <[email protected]>
Signed-off-by: John Molakvoæ (skjnldsv) <[email protected]>
Signed-off-by: John Molakvoæ (skjnldsv) <[email protected]>
Signed-off-by: John Molakvoæ (skjnldsv) <[email protected]>
Signed-off-by: Jan-Christoph Borchardt <[email protected]>
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 <[email protected]>
Signed-off-by: Jan-Christoph Borchardt <[email protected]>
Signed-off-by: John Molakvoæ (skjnldsv) <[email protected]>
Signed-off-by: John Molakvoæ (skjnldsv) <[email protected]>
719e977
to
876d6ec
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Rejoice; finally, the nitpicker is reasonably satisfied 👍
I hope Drone is too... :-P
🎉 I will merge once drone has done it's job 🎉 |
876d6ec
to
ef7d2a0
Compare
ef7d2a0
to
876d6ec
Compare
@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
.done
orsuccess
hooks 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