[rc6] Keep data attributes during resolving
See original GitHub issueAfter running the resolver, only displayed values are left, thanks to this piece of code:
return rows => rows.map(row => {
let ret = {};
resolvedColumns.forEach(column => {
ret = {
...ret,
...method(row, column)
};
});
return ret;
});
… but I need the rest of my data, too. Crucially, I need an id
field, which I don’t want displayed, but which I need for my onRow
click handler.
The best compromise in terms of annoyance/performance may be to allow users to define phantom columns that don’t get rendered.
In any case however, the rowKey
should be kept around. It’ll be id
in most cases anyway.
Issue Analytics
- State:
- Created 7 years ago
- Comments:10 (10 by maintainers)
Top Results From Across the Web
Using data attributes - Learn web development | MDN
HTML is designed with extensibility in mind for data that should be associated with a particular element but need not have any defined ......
Read more >Gradle 6.6-rc-6 Release Notes
The Gradle team is excited to announce Gradle 6.6-rc-6. This release introduces a major performance optimization as an experimental opt-in.
Read more >How to preserve the case of a data attribute? - Stack Overflow
Valid HTML data attributes can't contain uppercase characters anyway: From the W3: A custom data attribute is an attribute in no namespace ...
Read more >Directory Services 6.5 > Administration Guide
User attributes hold the information for users of the directory. ... DS servers resolve expressions at startup to determine the configuration.
Read more >Resources - Puppet
When Puppet applies a catalog to the target system, it manages every ... Attributes accept certain data types, such as strings, numbers, hashes,...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yeah, good point. Maybe the right thing to do is to overlay the resolved data on top of the other. So extra
...
. I think I’ll change the resolver that way.Thanks for the report again.
@skosch Thanks. Looks good. 👍