Skip to content

feat: create shortcut component that can be used on any page #2350

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
SgtPooki opened this issue Mar 17, 2025 · 2 comments · May be fixed by #2365
Open

feat: create shortcut component that can be used on any page #2350

SgtPooki opened this issue Mar 17, 2025 · 2 comments · May be fixed by #2365
Labels
P3 Low: Not priority right now

Comments

@SgtPooki
Copy link
Member

We need to take the shortcut functionality added by #2337 and ensure it is fully encapsulated into a component/context/hook that is flexible and can be used by both files list & grid view, as well as any other components that may need it (peers page, or any future pages)

@george-hub331
Copy link
Contributor

@SgtPooki should the shortcuts shown in the component be relevant shortcuts to the page its being viewed on or should it just be general shortcuts regardless of the page?

@SgtPooki
Copy link
Member Author

@george-hub331 I think we should probably have defaults for all pages, whatever those are, but ideally we would be able to customize them for specific actions on a page.

I imagine a react context with some hooks would be a good approach.

This is low priority though i would say.

@SgtPooki SgtPooki added the P3 Low: Not priority right now label Apr 4, 2025
@george-hub331 george-hub331 linked a pull request Apr 6, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P3 Low: Not priority right now
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants