-
Notifications
You must be signed in to change notification settings - Fork 159
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
Feature/copy #3749
Feature/copy #3749
Conversation
PR rebased and ready for review |
| "question?" | "folder-with-question?" | | ||
| "&and#hash" | "folder-with-&and#hash" | | ||
|
||
@skipOnOCIS @issue-3755 |
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.
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.
Looks good overall.
See my comment about "nice to have" test
isRowDisabled(resource) { | ||
const isBeingMoved = this.resources.some(item => item === resource.path) | ||
|
||
return resource.type !== 'folder' || !resource.canCreate() || isBeingMoved |
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.
nice, so your are indeed checking the perm on the target folder 👍
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.
would be good to add a test for the case(s) where a target folder is not targettable due to missing permissions (received read-only share)
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.
I've opened a ticket for collecting the next scenarios to test for copy and move. Should I add this in there or implement it already in this PR?
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.
later is fine, please label the ticket "QA-team" and ping Artur
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.
later... but within the sprint would be good because else I don't think we can consider the task "done"
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.
Really nice! 🚀 🎆
@@ -139,6 +140,12 @@ module.exports = { | |||
*/ | |||
move: function(target) { |
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.
Just seeing that the target
param is not used in the function body, so you could remove it.
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.
Must have overlooked this. Nice catch!
Fix promise and properly handle errors Add acceptance tests Merge move and copy in locationPicker tests Add batch copy Add copy file action in tests Fix copy error message Add permissions check for copy in public links Add permissions check for batch copy action in public links Fix copy file action in tests Fix error message in copy tests Add changelog Add translations context and adjust guides for copy Skip public links test in oCIS Remove target from move
Description
We've added copy action to the files list. It is possible now to copy folders and files.
The copy is executed via location picker.
Related Issue
How Has This Been Tested?
Types of changes
Open tasks: