Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(table): read selectable prop from each row by default #1321

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

kimjaej
Copy link

@kimjaej kimjaej commented Apr 12, 2022

Description

Read selectable prop from the row by default

Screenshots

Before After

Testing in sage-lib

Testing in kajabi-products

  1. (LOW/MEDIUM/HIGH/BREAKING) Description of the change and its impact with QA as the audience.
    • One more examples of the component in use to either test the change or verify the change has not had adverse effects.

Related

https://kajabi.atlassian.net/browse/MAN-2626

@monicawheeler
Copy link
Collaborator

@kimjaej - Hi there! Thanks for adding a PR in Sage. Could you provide a bit more information in the Conversation portion of the PR so that we may better understand and review your work so you can merge? Specifically, how do we test your change in Storybook, are there any visuals you can provide us a before/after, and does this change impact kajabi-products? Thank you so much and please reach out to #sage-support if you need any help or have any further questions!

@ju-Skinner ju-Skinner requested a review from a team December 6, 2022 15:12
@@ -278,7 +278,7 @@ export const Table = ({
cells={cells}
schema={schema}
selected={selfSelectedRows === SELECTION_TYPES.ALL || selfSelectedRows.includes(rowId)}
selectable={selectable}
selectable={!!(row.selectable || selectable)}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Curious about the double negation here. Is it the case that one or both of row.selectable and selectable aren't set as booleans? I'm basing this all off of the propTypes defs enforcement; unsure of what we're actually finding in-app.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants