Skip to content

[FEATURE REQUEST] Allow to go to the destination folder when the copy/move operation is finished#4802

Open
mykh-hailo wants to merge 7 commits intoowncloud:masterfrom
mykh-hailo:feat/copy_snack_bar
Open

[FEATURE REQUEST] Allow to go to the destination folder when the copy/move operation is finished#4802
mykh-hailo wants to merge 7 commits intoowncloud:masterfrom
mykh-hailo:feat/copy_snack_bar

Conversation

@mykh-hailo
Copy link
Contributor

@mykh-hailo mykh-hailo commented Mar 11, 2026

Related Issues

App: #4379

  • Add changelog files for the fixed issues in folder changelog/unreleased. More info here
  • Add feature to Release Notes in ReleaseNotesViewModel.kt creating a new ReleaseNote() with String resources (if required)

@mykh-hailo mykh-hailo force-pushed the feat/copy_snack_bar branch 2 times, most recently from b088f36 to 9a416e0 Compare March 11, 2026 03:46
@joragua
Copy link
Collaborator

joragua commented Mar 11, 2026

Thanks for your contribution @mykh-hailo! 🍻 Just a small note before the CR: please be careful with the branch name. The branch prefixes we use in the project are: feature/, fix/ , technical/ and improvement/. Do not forget to take a look to CONTRIBUTING.md to make sure everything follows the guidelines.

I will take care of this as soon as possible and I'll ping you when it's ready 😄

@mykh-hailo
Copy link
Contributor Author

@joragua I'd appreciate it if you share any feedback on the result.

@mykh-hailo
Copy link
Contributor Author

@joragua Can you check my PR please?

@joragua
Copy link
Collaborator

joragua commented Mar 16, 2026

@mykh-hailo I'll ping you when the CR is finished. Stay tuned! 😄

@mykh-hailo
Copy link
Contributor Author

@joragua Can you provide me any updates on this?
I like your fast feedback and update.
😄

@joragua
Copy link
Collaborator

joragua commented Mar 20, 2026

Hi @mykh-hailo! I'm working on the PR but it will not be available until next week. I'll ping you once it's done. No worries! 😄 Thanks for your patience!

Copy link
Collaborator

@joragua joragua left a comment

Choose a reason for hiding this comment

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

Nice job @mykh-hailo! 🙌🏻 Somme comments here.

NOTE: I'd add a release note since this is an important and useful improvement for end users. They should be aware of it this and see the new feature in the release notes screen. You can add a new entry in ReleaseNotesViewModel.kt with an appropriate title and subtitle. Let us know if you have any question about this process. 😄

} else {
showMessageInSnackbar(R.id.list_layout, message)
}
copyMoveTargetFolder = null
Copy link
Collaborator

Choose a reason for hiding this comment

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

Just a question: Is it necessary to set null at the end? Since the copyMoveTargetFolder value is set at the begin of requestMoveOperation and copyMoveOperation methods

Copy link
Collaborator

Choose a reason for hiding this comment

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

Just a question: Is it necessary to set null at the end? Since the copyMoveTargetFolder value is set at the begin of requestMoveOperation and copyMoveOperation methods

What about this? 🤔

@mykh-hailo mykh-hailo force-pushed the feat/copy_snack_bar branch 2 times, most recently from d886716 to a2d1b92 Compare March 23, 2026 14:27
@mykh-hailo
Copy link
Contributor Author

@joragua Thank you for your feedback.
I updated the code for it.
Could you check it please?

@mykh-hailo mykh-hailo requested a review from joragua March 24, 2026 07:07
joragua

This comment was marked as outdated.

Copy link
Collaborator

@joragua joragua left a comment

Choose a reason for hiding this comment

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

Some comments and it's ready @mykh-hailo! 😄

  1. We usually use refactor: prefix in commits when we change the code but keep the same behavior (string changes, method refactoring...) We use the prefix fix: when something is broken and we must fix it. My suggestion: refactor: update string resource

  2. The prefix used for release note is feat: since it's a new improvement in the app that end users can see. My suggestion: feat: add release note

You can do an interactive rebase and change the name of the commits applying my suggestions, in order to follow the project convention for commits. Let us know if you have any question about the process 🍻

Comment on lines +167 to +170
showSnackbarWithAction(
message = getString(R.string.sync_fail_ticker_unauthorized),
actionText = getString(R.string.auth_oauth_failure_snackbar_action),
action = {
Copy link
Collaborator

Choose a reason for hiding this comment

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

I think you removed the snackbar duration from here, and it should be displayed indefinite: duration = Snackbar.LENGTH_INDEFINITE

} else {
showMessageInSnackbar(R.id.list_layout, message)
}
copyMoveTargetFolder = null
Copy link
Collaborator

Choose a reason for hiding this comment

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

Just a question: Is it necessary to set null at the end? Since the copyMoveTargetFolder value is set at the begin of requestMoveOperation and copyMoveOperation methods

What about this? 🤔

<string name="move_file_invalid_into_descendent">It is not possible to move a folder into a descendant.</string>
<string name="move_file_invalid_overwrite">The file exists already in the destination folder.</string>
<string name="move_file_error">An error occurred while trying to move this file or folder.</string>
<string name="move_success_msg">File moved correctly</string>
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
<string name="move_success_msg">File moved correctly</string>
<string name="move_file_correctly">File moved correctly</string>

<string name="copy_file_invalid_into_descendent">It is not possible to copy a folder into a descendant.</string>
<string name="copy_file_invalid_overwrite">The file exists already in the destination folder.</string>
<string name="copy_file_error">An error occurred while trying to copy this file or folder.</string>
<string name="copy_success_msg">File copied correctly</string>
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
<string name="copy_success_msg">File copied correctly</string>
<string name="copy_file_correctly">File copied correctly</string>

Comment on lines +754 to +755
<string name="release_notes_4_8_0_title_action_to_copy_or_move_destination_folder">Action to copy/move destination folder</string>
<string name="release_notes_4_8_0_subtitle_action_to_copy_or_move_destination_folder">Added a snackbar action to quickly navigate to the destination folder after copy/move operations.</string>
Copy link
Collaborator

Choose a reason for hiding this comment

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

We don't usually include technical words in the release notes such as snackbar.

My suggesstion:

Suggested change
<string name="release_notes_4_8_0_title_action_to_copy_or_move_destination_folder">Action to copy/move destination folder</string>
<string name="release_notes_4_8_0_subtitle_action_to_copy_or_move_destination_folder">Added a snackbar action to quickly navigate to the destination folder after copy/move operations.</string>
<string name="release_notes_4_8_0_title_action_to_copy_or_move_destination_folder">Navigate to destination folder</string>
<string name="release_notes_4_8_0_subtitle_action_to_copy_or_move_destination_folder">New action to navigate to the destination folder when a file is copied or moved</string>

Do you have any idea for the release note @jesmrec? (open to discussion)

Copy link
Collaborator

Choose a reason for hiding this comment

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

That's right. Release notes target any kind of user, so, we can not assume that technical words are understood by everyone. Better to use basic language. About your approach, @joragua, it's ok with tiny changes from my side #

Suggested change
<string name="release_notes_4_8_0_title_action_to_copy_or_move_destination_folder">Action to copy/move destination folder</string>
<string name="release_notes_4_8_0_subtitle_action_to_copy_or_move_destination_folder">Added a snackbar action to quickly navigate to the destination folder after copy/move operations.</string>
<string name="release_notes_4_8_0_title_action_to_copy_or_move_destination_folder">Navigation to target folder</string>
<string name="release_notes_4_8_0_subtitle_action_to_copy_or_move_destination_folder">New action to navigate to the destination folder when a file or folder is copied or moved<</string>

Copy link
Collaborator

Choose a reason for hiding this comment

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

Nice! @mykh-hailo I'd go for the release note approach that @jesmrec commented 🙌🏻

@mykh-hailo mykh-hailo force-pushed the feat/copy_snack_bar branch from a2d1b92 to c394298 Compare March 26, 2026 12:43
@mykh-hailo mykh-hailo force-pushed the feat/copy_snack_bar branch from c394298 to 2468ae7 Compare March 26, 2026 12:46
@mykh-hailo mykh-hailo requested review from jesmrec and joragua March 26, 2026 12:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[FEATURE REQUEST] Allow to go to the destination folder when the copy/move operation is finished

3 participants