-
-
Notifications
You must be signed in to change notification settings - Fork 968
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
Nested locations currently not suported #2772
Comments
Already tracked, and we're still not sure how it will be supported (or if it will be supported to begin with). It will probably depend on user's demand for this feature. Especially because re-indexing a nested location with a ton of duplications, and a ton of duplicated sync messages doesn't make much sense, as these data would already be available in the parent location. |
Before we close this, I want to clarify and understand a bit more about this.
We could definitely stand to improve the user experience in this situation, and I'd like to better understand what the existing state was and what your expectations were. |
Gotcha. I now understand what the issue was. Indeed I had added Documents (and another called Downloads) to my locations list. I thought there were acting as shortcuts, not realizing I would cause double indexing. |
Check for other issues
Issue description
When I click the path next to the top folder icon, I get this message.
Steps to reproduce
See above
Platform and versions
Development tool versions (optional)
Stack trace
No response
Additional context
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: