Reassess unresolved notifications on folders bigger than set limit after applying new folder sync selection.
- Dominant language
- C++
- Stars
- 3.9k
- Forks
- 1k
- Avg merge
- 1d 17h
- Merged PRs (30d)
- 123
Description
### How to use GitHub
* Please use the 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to show that you are interested into the same feature.
* Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
* Subscribe to receive notifications on status change and new comments.
---
## Feature request
**Which Nextcloud Version are you currently using:** (see administration page)
33.0.5. on Windows
**Is your feature request related to a problem? Please describe.**
After disabling VFS all folders are selected for sync. You may receive notifications on folders bigger than the set limit. These notifications offer a sync/stop sync choice. You may first have set a new selection of folders to sync before handling these notifications. Pressing sync, works logically, by syncing this folder, whether you had it selected or not. But having this choice conflicts with the expectations after the earlier selection of folders, despite the technical logic of the persistence of these notifications, which is based on the order of events.
**Describe the solution you'd like**
It would be better if older notifications on large folders that are not in the earlier applied selection are resolved automatically with a don't sync action with the application of a new selection of folders to be synced.
**Describe alternatives you've considered**
The alternative is the current state, where you have to check the notifications for both related content and size, instead of just size.
**Additional context**
Add any other context or screenshots about the feature request here.
Contributor guide
Assessment
This issue has not been assessed yet.