oxidecomputer / oxidecomputer/console

Tracking: Quick actions (command palette)

Open
#1,352 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

tracking
Dominant language
TypeScript
Stars
228
Forks
22
Avg merge
19h 42m
Merged PRs (30d)
32

Description

We have a command palette that seemed very cool at the time, but we have (reasonably and unsurprisingly) failed to keep it up to date with all the things you can do in the console. We need to do some thinking about whether any investment here is worth it for MVP — probably not considering it's ultimately a nice-to-have. Feels more like an MVP+1 thing. In that case, we should consider whether the command palette is complete enough as-is (or with minimal additional work to add a few more actions on a few more pages) to warrant leaving in, or we should turn it off altogether until we can make it good.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Review the existing command palette and compare its available actions with actions exposed across the console pages; done means deciding whether a small, defined set of additions makes it complete enough to keep, or whether it should be turned off.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.