Path specific file sytem setup

How to use GitHub

• Please use the 👍 reaction 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.

Description

The objective of this issue is to introduce path-scoped mount setup so mount providers no longer have to provide all mounts for a user when setting up for a specific path. To achieve this, the SetupManager should resolve mounts for a specific path by consulting the mounts table to retrieve the closest parent with a mount, call the responsible mount provider to initialize it, and finally stop registering mounts itself.

For this reason Mount Providers will need a getMountsForPaths method.

It may also be necessary to have the mount schema track parent–child relationships to make looking up the nearest ancestor efficient.

Note: the changes mentioned here MUST happen in a non-breaking format. It is NOT an option to edit existing interfaces. For this purpose new interfaces can be created and extend the existing ones.

Start by tracing SetupManager, the mount providers, and the mounts table schema to understand how mounts are currently resolved and registered. Check how a provider could expose getMountsForPaths without changing existing interfaces. Done means path-scoped setup resolves the closest parent mount, initializes it through the responsible provider, and preserves compatibility with existing interfaces.