question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Fails after upgrading to v6.9.0 or later

See original GitHub issue

Using v6?

Yes

Using v7?

No. However, tried with v7.0.0-alpha.2, and this issue exists.

Describe the bug When updating from v6.8.6 to v6.9.0, pages with react-table fails with following error,

Cell(...): Nothing was returned from render. This usually means a return statement is missing. Or, to render nothing, return null.

Update (2019 Mar 11): Further investigation suggests that, this error appears if one or more data fields required in react-table column list are missing.

Example, assume a table that renders columns id and line. If the JSON data fed into table has entries where either id or line key-value pairs are missing, entire rendering process fails with above error.

v6.8.6 and prior were able to render empty column/cell fields, if relevant data is unavailable. It seems, this safe guard is unavailable from v6.9.0 onwards.

To Reproduce Steps to reproduce the behavior:

  1. Prepare a working React app with react-table (v6.8.6)
  2. Implement a page with working table
  3. Install newer react-table version, v6.9.0 or higher using npm
  4. Try to access page implemented in step 2
  5. See error, should be as or similar to screenshot below

Expected behavior Should work flawlessly as in react-table v6.8.6.

Codesandbox!

Update (2019 Mar 11): Code sample to re-produce this bug is now available here.

Screenshots image

Desktop (please complete the following information):

  • OS: Windows 10
  • Browser: Google Chrome
  • Version: v72 and above

Smartphone (please complete the following information): N.A.

Additional context N.A.

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Reactions:2
  • Comments:10

github_iconTop GitHub Comments

3reactions
tannerlinsleycommented, Apr 23, 2019

I’m doing that right now actually. I plan on releasing a 6.10.0 that is a rollback + some cherry picked commits that are stable.

1reaction
MatthewHerbstcommented, Apr 23, 2019

@tannerlinsley you could publish a 6.9.1 that is a rollback to 6.8.6 so that everyone is fixed, not just the people reporting the issue

Read more comments on GitHub >

github_iconTop Results From Across the Web

Fails after upgrading to v6.9.0 or later · Issue #1286 - GitHub
If the JSON data fed into table has entries where either id or line key-value pairs are missing, entire rendering process fails with...
Read more >
Upgrading Node.js to latest version - Stack Overflow
After complete the installation above, the NodeJS and NPM will be upgraded to the latest one and then you can cleanup the package...
Read more >
FortiOS 6.2.9 Release Notes - Amazon AWS
When you upgrade to FortiOS 6.2.9 and later, the default ssl-min-proto-version option is TLS v1.2. The following.
Read more >
Important Upgrade Notes - Mattermost Documentation
On MySQL, if you encounter an error “Failed to apply database migrations” when upgrading to v6.4.0, it means that there is a mismatch...
Read more >
Release Notes for the Cisco ASA Series, 9.14(x)
If the upgrade is not complete within 30 minutes or it fails, contact Cisco technical support; do not power cycle or reset the...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found