Open ZarkoPernar opened 1 year ago
After discussing this with Josh, we decided to make sure we showcase in storybook, and make clear in the documentation, that we currently only support a single button per column. Multiple buttons per columns will require a refactor of editable cells, and addition of an additional type of a cell which is a considerable piece of work. The single button on the other hand requires a minimal amount of code change.
March 28 - still addressing a bug on this ; create a new ticket to refactor. this is ok to close March 23 - awaiting reviews March 22 - awaiting reviews March 20 - on pause until validation complete March 17 - not in progress currently March 14 - another PR to close out - discussions first to ensure this is the path to move fwd with March 13 - addressing feedback today March 1- awaiting reviews Feb 28 - awaiting dev review Feb 17 - awaiting dev review - josh Feb 16 - awaiting dev review - Josh 2/15 - awaiting dev review - josh 2/14 - requires dev reviews 2/13 - working on tests now; stella can take a look at this when she can 2/9 - Josh to review 2/8 - update that Josh needs to review (Zarko to add to PR)
Discussion to happen today on Tooltip issues, that are blocking this
I have now removed the Tooltip from the example because in its current form does not work inside grid, and the bug I mentioned in yesterday's standup was related to the tooltip. I have refactored the story and should now be done.
So, can this issue be marked as "done" or pulled back "in progress"?
fyi @joshwooding
I found more issues with the naive approach attempted in #1036. I suggest we close the PR and focus on redesigning the approach to interact-able cells first. cc @parsakhan21
Area
UI Components
The problem
Currently, users can add both individual buttons and button groups to editable cells. We need to ensure there is sufficient documentation, story examples, and that the code makes sense for this use case.
The solution
Alternatives and examples
N/A
Are you a JPMorgan Chase & Co. employee?