Resource page table header cell layout inconsistencies
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Refactor
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- typescript
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.
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:
anti-affinity group ID cell is on right:
In #3260 we add it to the VPC page, on the left:
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.
- Dominant language
- TypeScript
- Stars
- 228
- Forks
- 22
- Avg merge
- 8h 59m
- Merged PRs (30d)
- 21
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from oxidecomputer/console
-
Disks: Disable 'Size' field when selecting 'Make disk read-only' and 'Image'/'Snapshot' as a sourcePossibly taken @david-crespo claimed this 2 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
oxidecomputer/console#3391 · 3 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
Alerting > Receivers: Error message for subscriptions gets hidden by empty dropdown when zoomed outOpen
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
oxidecomputer/console#3390 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 Half a day Newbie friendliness 72/100
oxidecomputer/console#3375 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
oxidecomputer/console#3338 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
oxidecomputer/console#3327 · 2 comments ·
Maintainers usually reply within 1 day
All issues in oxidecomputer/console
Similar issues
-
enhancement providers-api ui-dashboard
Difficulty 2/5 1-3 hours Newbie friendliness 61/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
external-issue to-triage
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
needs triage
Difficulty 1/5 Under an hour Newbie friendliness 88/100
homarr-labs/homarr#6976 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day