Rows are not rendering after upgrading from 0.3.1 to 0.5
See original GitHub issueI think the switch from underscore to lodash may have caused some issues. For example, in gridRow.jsx I noticed in the render method line 81 _.object was changed to fromPairs. These methods do not work the same and so it causes issues like the one below:
// If columns is flat array ['one', 'two', 'three']
fromPairs(columns, []) // => { o: "n", t: "h" }
// Expected output is
{
'one': undefined,
'two': undefined,
'three': undefined
}
I think zipObject method would work instead
Issue Analytics
- State:
- Created 7 years ago
- Comments:9 (2 by maintainers)
Top Results From Across the Web
App does not render after update to 0.4.14 #9119 - GitHub
After applying the latest version bump on our local instance (v0.4.14), we cannot use Backstage - the app gets rendered through an 'empty ......
Read more >Table Component is not re-rendered after state update
Problem was here as OP has already deduced. const evaluationResults = state.evaluationResults;. This was causing a state-mutation which goes ...
Read more >Examples • reactable - GitHub Pages
You can make rows expandable with additional content through details , which takes an R or JavaScript render function. See Custom Rendering for...
Read more >Fix list for IBM WebSphere Application Server traditional V9
MQ JMS in CICS JVM server working with OSGI bundles fails with RC2058 MQRC_Q_MGR_NAME_ERROR. PH31692, Not all message listeners started in the control...
Read more >SportsPress Pro Changelog - ThemeBoy Support
Fix - Performance format not updating. ... Fix - OpenStreetMap not displaying map after update. ... Fix - Videos embedded in post content...
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 Free
Top 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

@anaximander Thanks for the PR and clarification. Glad this was resolved.
Just opened a PR to fix this… I think there was a bit of a communication breakdown between @adamgruber and @atapatel. When @atapatel said “i don’t think so zipObject will work in this situations.”, he meant “I don’t think so. zipObject will work in this situation” which appeared to have been interpreted by @adamgruber as “I don’t think zipObject will work in this situation”.
Let me know if there are any concerns with the PR, happy to update it as needed.