Folder on web isn't deleted after sync & on first action
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Domain
- backend
Research direction
Reproduce the sequence described: create an online folder, import tracks, sync, delete the folder and tracks on the device, then sync again. Trace the web sync handling for folder and track deletions; done means both the tracks and their folder are removed online after the second sync. No files or tests are named, so locating the relevant sync entry point is part of the work.
Written by the indexing model from the issue text.
Description
I´ve created an online folder, then imported some tracks in it.
Next, I ran a sync on my device, folder and tracks got synced to the device correctly.
Later I deleted the folder and it´s tracks on my device and ran a sync again.
Result: online the tracks were deleted, but the folder remains - and is not deleted at a sync.
- Dominant language
- MDX
- Stars
- 63
- Forks
- 431
- Avg merge
- 17h 10m
- Merged PRs (30d)
- 124
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from osmandapp/web
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
Enlarge click area for selecting track lines in mapPossibly taken @Dima-1 claimed this 17 days ago. OpenNice to have
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
osmandapp/web#2057 · 2 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
prime-radiant-inc/evener#6241 ·
Maintainers usually reply within 1 day
-
Type: Bug
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
MovingBlocks/Terasology#5415 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
Maintainers usually reply within 1 day
-
bug maintainer-managed
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
awslabs/visual-asset-management-system#1417 ·
Maintainers usually reply within 1 day