Closed elycheea closed 1 year ago
This is a list of scenarios we should demonstrate in our stories but some of these may not require a separate story (e.g. alignment, truncation)
For PageHeader
or Tabs
as table header, should double check accessibility.
AKA Row height settings
Row height settings
or Row size settings
Sticky action column
Is Hover on Row
uses text as exampleSelect all across all pages in the toolbar not implemented at this time (Carbon). More does not use caret yet due to limitations in ButtonMenu.
Expandable row
Nested table
story1ch
?Keyboard navigation may overlap with that of inline editing.
Tearsheet
instead of Modal
, spacing, colors, some interactive bugs)Tearsheet
Can either use the default basic table story or one alignment story
To be defined.
Ability to handle thousands of entries.
Adding a shortened list of extensions we need to add with it's own extension directory in storybook
@AlexanderMelox Most of these are covered in the design reviews, but keeping us on the hook to ensure we don’t miss anything.
What will this achieve?
Allow users to have more control over datagrid settings. Currently, the controls only use the
datagridState
but it provides no way view use cases and examples that the datagrid hooks provide.How will success be measured?
For each story, users should be able to view scenarios matching those described in the in design specs.
Additional information