-
Notifications
You must be signed in to change notification settings - Fork 12
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
fix(table): pass down value and record types to cells #401
Conversation
✅ Deploy Preview for sefirot-story ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for sefirot-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
onClick(record: R): void | ||
show?(record: R): boolean |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
these are pretty inconsistent with others. thinking consistency vs usability 🤔 (value even if introduced will always be undefined)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmmmm I vote for usability here. Also, I have a feeling we could remove value
from everywhere in the future version.
Since we started using Ops pattern, I see my self barely using value
anymore because ops requires whole model to be passed in 🤔
{
cell: (_, user) => ({
value: userOps.fullName(user)
})
}
No description provided.