seas-computing / seas-computing/mark-one

Update Table Components for Sizing

Open
#214 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement Frontend
Dominant language
TypeScript
Stars
0
Forks
1
PR merge metrics
No merged PRs in 30d

Description

Description

We need to make some modifications to our Table components so that we can prevent tables from shrinking or stretching as table content changes within the page. We also want to be able to set specific widths on certain columns (i.e. keeping columns with icons tight to that content while other columns may need more space, as shown here for example).

We might look at:

  • using the table-layout: fixed property on the table itself to lock it to an overall width
  • allowing columns to use percentages to set width to fit a certain size
  • implementing some of the functionality that was part of this (now deleted) TableWrapper component (minus the border-collapse property).

Ideally we can accomplish this without creating new components, but new components can be added if necessary.

Acceptance Criteria
  • we are able to lock the table to an overall width, even if its content changes
  • we are able to set columns to specific widths
Accessibility Criteria

Check the DAS guidelines on data tables

Additional Context

This conversation in mark-one might be helpful to look at as well.


  • Test
  • Docs

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 reviewing the current Table components and the deleted src/client/components/layout/TableWrapper.ts, then read the linked mark-one conversation and the table-layout guidance. Done means tables retain an overall width as content changes and selected columns accept specific widths, with accessibility criteria and tests or docs addressed.

Written by the indexing model from the issue text.

Assessment

Tech stack
react, typescript
Domain
frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.