2021-10-07 Meeting notes

Owned by Adam Stankiewicz, created
Last updated: Oct 07, 2021 by Gabriel Weinberg
1 min read

Date

Oct 7, 2021

Participants

  • @Adam Stankiewicz

  • @Gabriel Weinberg

Goals

  •  

Discussion topics

Time

Item

Presenter

Notes

Time

Item

Presenter

Notes

 

Card.Header

Long

  • Is it hard to support responsive if you can pass any node into the component?

  • There are use cases for supporting buttons in addition to iconbuttons in the header

  • overflow menu is a little restrictive in its behavior

  • If we let nodes pass into the header, we shouldn't restrict the overflow menu

  • Manny: Maybe the Collapsible Button Group type behavior in DataTable (e.g., overflow menu) is its own components that could be used by the consumer.

  •  

10-15 min

Bulk Enrollment V2

Amy

  • Gut check needed for use of Paragon components

    • can use the table action to pass in a disabled state

Action items

Design spec for the card header should guide designers on best practice for how to bring a component into the header row @Gabriel Weinberg Note: Whatever is passed into the row will stay top aligned.
Look into adding a separate Collapsible Button Group type of component that could be used within DataTable, Card.Header, etc. (from Figma library and implementation)

Decisions

  1. Card header should be able to accept any component, not just an icon button or standard button.
  2. Data Table table action can be used to pass a disabled button state into the row