Skip to content

Conversation

@rummatee
Copy link
Contributor

@rummatee rummatee commented Nov 9, 2018

This my first time contributing to Nextcloud and using Pull Requests, so please tell me, if I did something wrong.
This Pull Request intends to solve Issue #11314 .
I changed the signature of the filepicker, but made sure that the behavior doesn't change in case it gets called without the additional argument.

@ChristophWurst ChristophWurst added this to the Nextcloud 16 milestone Nov 12, 2018
@rummatee
Copy link
Contributor Author

please review @jancborchardt

@jancborchardt
Copy link
Member

Aaaalright @rummatee, sorry for the belated reply but welcome to Nextcloud! 👋 🎉

Will get right to reviewing, also cc other @nextcloud/designers, and this definitely also needs a JS review from @nextcloud/javascript.

@jancborchardt
Copy link
Member

@rummatee also, could you rebase onto latest master, as there were some changes? Let me know if you have questions how to do that – I generally also search and find the answer on StackOverflow 😅

@jancborchardt
Copy link
Member

Hmm, just tested it and it doesn’t seem to work? Still starts in the root folder every time. Do I need to compile anything? :)

@rummatee
Copy link
Contributor Author

@rummatee also, could you rebase onto latest master, as there were some changes? Let me know if you have questions how to do that – I generally also search and find the answer on StackOverflow sweat_smile

indeed I would appreciate some help on this. I see that there is a button to resolve conflicts, but when I do that, it shows me a warning that I am committing to master and I was afraid to confirm that.

Hmm, just tested it and it doesn’t seem to work? Still starts in the root folder every time. Do I need to compile anything? :)

I don't think it should require to compile anything. I just tested it again and for me it works. I created a folder called "test" and a file in this folder. When I want to move this file the dialog starts in folder "test".

@jancborchardt
Copy link
Member

indeed I would appreciate some help on this. I see that there is a button to resolve conflicts, but when I do that, it shows me a warning that I am committing to master and I was afraid to confirm that.

It’s fine – that is referring to your master branch. It’s not possible for anyone to commit directly to master or any stable branches as we have branch protection enabled. :)

@kesselb
Copy link
Contributor

kesselb commented Dec 22, 2018

A: Select one file, use the three dot menu on the right, pick copy or move ✅
image

B: Select two ore more files, use the top three dot menu, pick copy or move ❌
image

A is working fine for me but B does not work.

Copy link
Contributor

@kesselb kesselb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great improvement 👍

@rummatee
Copy link
Contributor Author

A is working fine for me but B does not work.

okay thank you for clarifying that there are 2 different menus that need this feature. The new commit should add it also to the multiselect menu.

@jancborchardt
Copy link
Member

Thanks @rummatee!

We definitely need a code review on this from someone in @nextcloud/javascript :)

@kesselb
Copy link
Contributor

kesselb commented Dec 23, 2018

Select two or more files, use top three dot menu and pick "move or copy". Please note the two buttons "move" and "copy".
image

When you go a directory higher or lower the button label is changed like below even when you are in the same folder again.

image

I think the button labels should be the same @jancborchardt

@jancborchardt
Copy link
Member

I think the button labels should be the same

Yes, true. Is it possible to make it so that in the folder where the files are right now, they are simply "Copy" and "Move"? Ideally they should also be disabled there, and a tooltip (also visible on click) on the buttons should say "This folder is the current place of the files."

@rummatee
Copy link
Contributor Author

I think the button labels should be the same

Yes, true. Is it possible to make it so that in the folder where the files are right now, they are simply "Copy" and "Move"? Ideally they should also be disabled there, and a tooltip (also visible on click) on the buttons should say "This folder is the current place of the files."

Well that would be related to issue #11313 #9931 and PR #10825 so I am not completely sure how these would interact. Of course it would be possible to change the label or grey out the buttons, but maybe it is better to leave that out of this PR to avoid conflicts with other PRs?

@jancborchardt
Copy link
Member

maybe it is better to leave that out of this PR to avoid conflicts with other PRs?

Good point, yes let’s do it separately!

Still waiting for a code review from @nextcloud/javascript :) @juliushaertl @danxuliu @kevgathuku @ChristophWurst anyone?

@rummatee rummatee force-pushed the master branch 2 times, most recently from 02dda9c to 00032b2 Compare January 5, 2019 17:40
Copy link
Member

@ChristophWurst ChristophWurst left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:)


var actions = this.isSelectedMovable() ? OC.dialogs.FILEPICKER_TYPE_COPY_MOVE : OC.dialogs.FILEPICKER_TYPE_COPY;
var dialogDir = self.getCurrentDirectory();
if (typeof self.dirInfo.dirLastCopiedTo !== undefined) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
if (typeof self.dirInfo.dirLastCopiedTo !== undefined) {
if (typeof self.dirInfo.dirLastCopiedTo !== 'undefined') {

@rummatee rummatee force-pushed the master branch 3 times, most recently from 17d9b9a to 6aa505b Compare January 8, 2019 14:30
Copy link
Member

@ChristophWurst ChristophWurst left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code looks good!

@jancborchardt
Copy link
Member

Here too @rullzer @MorrisJobke what about the Drone failure? Is it just unrelated?

@MorrisJobke
Copy link
Member

The failures are fixed on master already (issue with the PHP 7.0 to 7.3 compatibility). Either rebase or we can just assume that they will work and this is then ready for review and merge.

@MorrisJobke
Copy link
Member

@rummatee It seems that your force push closed this PR 🙈 Could you open a new one?

@rummatee
Copy link
Contributor Author

rummatee commented Jan 9, 2019

yeah, I didn't see the rebase conflicts and accidentally pushed to remove all my commits

@rummatee
Copy link
Contributor Author

rummatee commented Jan 9, 2019

hmm does it show my commits again when I click on reopen?

@rummatee rummatee reopened this Jan 9, 2019
@rummatee
Copy link
Contributor Author

rummatee commented Jan 9, 2019

@rummatee It seems that your force push closed this PR see_no_evil Could you open a new one?

now that I reopened it, it doesn't seem to run the checks. Do I have to create a new PR?

@MorrisJobke
Copy link
Member

now that I reopened it, it doesn't seem to run the checks. Do I have to create a new PR?

Or rebase again 🙈

@rummatee rummatee force-pushed the master branch 2 times, most recently from db81573 to cc8d539 Compare January 10, 2019 12:31
Copy link
Member

@juliusknorr juliusknorr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Small nitpick. Otherwise works as expected and the code looks fine 👍

@juliusknorr juliusknorr added 4. to release Ready to be released and/or waiting for tests to finish and removed 3. to review Waiting for reviews labels Jan 18, 2019
@juliusknorr
Copy link
Member

Signed-off messages are fine. DCO bot seems to have some issues. 😉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

4. to release Ready to be released and/or waiting for tests to finish enhancement

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants