Nested locations currently not suported

[Fusion]

Check for other issues

• I've checked for other issues, and none exist.

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

• OS: MacOS
• Spacedrive: v0.4.2

Development tool versions (optional)

Stack trace

No response

Additional context

No response

Code of Conduct

• I agree to follow the Code of Conduct.

[linear]

ENG-1938 Nested locations currently not suported

[fogodev]

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.

[iLynxcat]

Before we close this, I want to clarify and understand a bit more about this.

1. Do you already add another folder within your user folder as an indexed location such as /Users/chris/Desktop, Documents, Pictures, etc?
2. If yes, were you trying to add both those subfolders and the parent user folder as locations, or did you expect them to merge?

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.

[Fusion]

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.

[Fusion]

Hmm I just realized:

[brigazvi]

I just downloaded Spacedrive and ran into this problem. maybe I do not fully understand the vision of the app already. but I thought it was kind of super file explorer that contained my Google Drive in it. but I couldn't get to the programFiles folder which seems essential to me. but maybe I should use this app along with File Explorer. sound cumbersome. can anyone explain this to me?
(besides this problem, the app looks cool as hell. Also I'm familiar with some of the stack (React, Tauri, Typescript) which makes it even more interesting.