-
Notifications
You must be signed in to change notification settings - Fork 24
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
Feature Request: Cell/Header Attributes #204
Comments
@huntabyte he seems to be pretty busy lately, but he answered and merged some of my PRs not long ago. For the record, I've been using simple components like |
I'm just curious on his insights if this should be a plugin or part of the column definition! |
I personally think a plugin would make sense as it would be tree shakable and the design of the plugin system is well adapted for this kind of functionality. |
The
createRender
function is nice for rendering full-blown components, sometimes all you need is adata-*
attribute orclass
to get the cell where you want it. These attributes could be merged with the ones already provided by the library to spread onto the various elements.Something along the lines of this:
Where the
Attrs
takes the same params as the respective render properties, but expects aRecord<string, unknown>
or similar.If this is something you'd be willing to accept into the library, I'm more than happy to submit a PR - just want your blessing before spending the time @bryanmylee!
The text was updated successfully, but these errors were encountered: