-
-
Notifications
You must be signed in to change notification settings - Fork 155
Decouple quick actions from buttons #3802
Copy link
Copy link
Open
Labels
Priority: LowLow priority, I may not have time to implement these or are likely years away.Low priority, I may not have time to implement these or are likely years away.Size: MediumMedium size, requires some design, planning, and a moderate amount of code.Medium size, requires some design, planning, and a moderate amount of code.Status: ResearchMore research is needed before implementation can be doneMore research is needed before implementation can be doneSubtype: Quick ActionType: Technical DebtTechnical debt - code changes that aren't user facing (ex. refactoring)Technical debt - code changes that aren't user facing (ex. refactoring)
Description
Metadata
Metadata
Assignees
Labels
Priority: LowLow priority, I may not have time to implement these or are likely years away.Low priority, I may not have time to implement these or are likely years away.Size: MediumMedium size, requires some design, planning, and a moderate amount of code.Medium size, requires some design, planning, and a moderate amount of code.Status: ResearchMore research is needed before implementation can be doneMore research is needed before implementation can be doneSubtype: Quick ActionType: Technical DebtTechnical debt - code changes that aren't user facing (ex. refactoring)Technical debt - code changes that aren't user facing (ex. refactoring)
There's likely a better interface for quick actions that decouple it from the UI.
Most quick actions consist of a state and action. There are UI pieces are supporting, but not the quick action themselves.
Maybe the right abstraction is a QuickActionButton is the UI and the QuickAction (or ToolAction) is the logic.
More research needed to see if this is even worth splitting out. Splitting would enable easier integration into app shortcuts and assistant integration.