Repository navigation
Conversation
Resource types now return the ways an actor has access to their resources. A check without access entries asks the resource type instead of allowing all permissions of the type, so callers no longer have to intersect the result with the access they grant. An empty list of entries means no access. Assisted-by: ClaudeCode:claude-fable-5-2 Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
`NCU\Resource\Permission\IAccessManager` returns the access an actor was given to resources before any restriction, so apps do not have to ask the resource types themselves. Assisted-by: ClaudeCode:claude-fable-5-2 Signed-off-by: Ferdinand Thiessen <opensource@fthiessen.de>
|
This change is very problematic as it would completely undo all the performance improvements we did in the last year, since it would require resource providers to always resolve access origin for resources, which for files requires retrieving shares and mount information from all apps. I think we need to support providing cached/aggregated permissions initially and avoid at all costs this expensive eager-loading. The only reason why it is currently required is because of the |
That is already covered for exactly that reason: You can pass cached permissions as the
No its also to hook in unified sharing. Thats even the main idea: |
Summary
Resource types now return the ways an actor has access to their resources. A check without access entries asks the resource type instead of allowing all permissions of the type, so callers no longer have to intersect the result with the access they grant. An empty list of entries means no access.
The use case is also to later make it easy to plugin unified sharing for resolving access.
Checklist
3. to review, feature component)stable32)AI (if applicable)