Tracking: Alerts list improvements

Open
#3,381 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
typescript
Domain
frontend

Research direction

Start with the alerts list view and the audit logs page, then compare their table, pagination, virtualization, and side-modal behavior. Break the checklist into separate addressable changes for shared components, time filtering, and alert class filtering; treat the class-version explanation as an open decision. Done should be defined separately for each accepted item.

Written by the indexing model from the issue text.

Description

Some followups from #3320 related to fleshing out the alert list view. This may break out into a few directly addressable issues (some grouped together, even).

  • Componentize similarities with the audit logs page. The gist here is that these are both event lists, so we ought to have component structure to share the table style, pagination, virtualization, special side modal, etc.
  • Time filtering for the alerts page. This could arguably be handled in tandem with the audit logs page refactoring!
  • Alert class filtering for the alerts page. This one is distinct from the audit log refactor, but somewhat related (and should probably occur serially with that refactor, though the order shouldn't be important).
  • Class version may need some explanation. We may not take action here; people who need to care about the class version will likely have a much easier time understanding what it means. But noting the concern.
Dominant language
TypeScript
Stars
228
Forks
22
Avg merge
19h 42m
Merged PRs (30d)
32

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.

More from oxidecomputer/console

All issues in oxidecomputer/console

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.