Skip to content
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

Moving nested folders does not cleanup after move operation #102

Open
7 tasks done
piu130 opened this issue May 24, 2024 · 1 comment
Open
7 tasks done

Moving nested folders does not cleanup after move operation #102

piu130 opened this issue May 24, 2024 · 1 comment
Labels
bug Something is not working

Comments

@piu130
Copy link

piu130 commented May 24, 2024

Checklist

  • I can reproduce the bug with the latest version given here.
  • I made sure that there are no existing issues - open or closed - to which I could contribute my information.
  • I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
  • I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
  • I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
  • This issue contains only one bug.
  • I have read and understood the contribution guidelines.

Affected app version

1.0.1

Affected Android/Custom ROM version

LineageOS 21

Affected device model

OnePlus 6

How did you install the app?

F-Droid / IzzyOnDroid

Steps to reproduce the bug

  • Create a folder a and b.
  • Create a folder c inside a folder b.
  • Create a file d.txt inside folder c. (./b/c/d.txt).
  • Move folder ./b to ./a.

Expected behavior

Folder structure of . is ./a/b/c/d.txt.

Actual behavior

Folder structure of . is ./a/b/c/d.txt but ./b/c still exists.
./b and ./b/c should be removed after the moving operation.

Screenshots/Screen recordings

No response

Additional information

When moving a folder with depth one (eg. ./a/b.txt) the folder (./a) is removed and it works correctly.

@piu130 piu130 added bug Something is not working needs triage Issue is not yet ready for PR authors to take up labels May 24, 2024
@Aga-C Aga-C removed the needs triage Issue is not yet ready for PR authors to take up label May 24, 2024
@duttyend
Copy link

duttyend commented Dec 8, 2024

I've just experienced the exact same thing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something is not working
Projects
None yet
Development

No branches or pull requests

3 participants