JohnathanWeisner commented 1 year ago

Short Description

A Table component that handles all the visual pieces for a Table. This will eventually be a requirement to replace Semantic UI.

Requirements

Indirect sorting/filtering
Ability to paginate

Mockup

TK

Responsibilities

This component should be responsible for the following: TK

This component should NOT be responsible for... TK

Props Signature

<Component
  propA={}
  propB={}

Component.propTypes = {
}

akdetrick commented 1 year ago

Table usage in Narmi product

Lots of things look like tables. Does it mean they should all be handled by the same component? No. This comment is an attempt to audit table-like things in our product to figure out what component(s) NDS should provide for each kind of usage, if at all.

Balance table

It may look like a table in UI, but it's more of a list with a heading and actions on each item.

Table head doesn't list column labels; it lists category and total
Table head has a menubutton for custom sorting (sort controls are not on column heads)
Table head sometimes acts as a summary in a summary/details control
Whole row is clickable to get to a specific account
Each table row of data (account) has an actions menubutton (favorite, hide)
Never paginated

Transaction table (dashboard)

Static standard table that could be expressed using actual table elements.

Table head contains column labels
Whole rows are clickable
No table-level or row-level actions
Needs to support pagination

Transaction table (account)

Mostly the same as the dashboard transaction table except sorting and filtering controls are above the tabs.

Details list

Not really a table, but shares some similar styling. We should probably name this (with design team buy in) and make it a separate component from any table components.