Skip to content

Composable useFileActionsDelete can only be used by the files app #1806

@kulmann

Description

@kulmann

Initial Checklist

  • I understand this is a bug report and questions should be posted in the Community Discussions
  • I searched issues and couldn’t find anything (or linked relevant results below)

Bug Description

The isVisible callback of the useFileActionsDelete composable is very restrictive. It requires one of three routes of the files app to be the current route. This makes the composable unusable in other apps.

Reproduction Steps

  1. Embed useFileActionsDelete composable in another app
  2. Call isVisible of the actions correctly with space and resources in actionOptions

Expected Outcome

A Delete action becomes available on files or folders the current user has write access to

Actual Outcome

No Delete action becomes available, ever.

Metadata

Metadata

Assignees

Type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions