oxidecomputer / oxidecomputer/console

Resource page table header cell layout inconsistencies

Open
#3,268 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

In our resource pages, we often have a table at the top of the page with info about the resource
instances ID cell is on left:
Image

anti-affinity group ID cell is on right:
Image

In #3260 we add it to the VPC page, on the left:
Image

So there isn't currently a consistent layout placement for the ID, though it is in the last row on each of the pages.

There's also not a consistent practice around "created" date vs "last modified" date. Presumably, one is used over the other when it provides some added utility ("I just changed this resource; is that reflected in the last modified date?". With the change to the VPC page header (screenshot above), all datetime cells I could finds are on the right side, at least.

These aren't major, but could be worth thinking through so there's more consistency with them.

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

Start by comparing the resource page tables shown in the issue with the VPC page header. Determine a consistent placement for ID and datetime cells and whether “created” or “last modified” is the appropriate convention. Done means the convention is agreed and applied consistently across the affected resource pages.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
design, frontend
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.