Skip to content
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

[ListView] Cryptic errors from renderHeader and renderSectionHeader #1379

Closed
ccheever opened this issue May 23, 2015 · 4 comments
Closed

[ListView] Cryptic errors from renderHeader and renderSectionHeader #1379

ccheever opened this issue May 23, 2015 · 4 comments
Labels
Resolution: Locked This issue was locked by the bot.

Comments

@ccheever
Copy link
Contributor

If you try throwing an error from an implementation of renderRow or renderSectionHeader in a ListView, you get a very cryptic error message with a stack trace that doesn't point to the problematic code at all.

A similar problem also occurs if either of those methods returns undefined.

It would be good if those weren't so cryptic (maybe wrapped in a try/catch?).

@brentvatne brentvatne changed the title In ListView, if renderRow or renderSectionHeader throw Errors, the message to the developer is cryptic and hard to debug [ListView] Cryptic errors from renderHeader and renderSectionHeader May 29, 2015
@brentvatne
Copy link
Collaborator

@ccheever - Have any time to put together a PR to fix this? High quality error messages are very important for dev workflow 😄

@ccheever
Copy link
Contributor Author

@brentvatne - sorry haven't had time yet :/

@brentvatne
Copy link
Collaborator

💃

@mkonicek
Copy link
Contributor

Hi there! This issue is being closed because it has been inactive for a while.

But don't worry, it will live on with ProductPains! Check out its new home: https://productpains.com/post/react-native/listview-cryptic-errors-from-renderheader-and-rendersectionheader

ProductPains helps the community prioritize the most important issues thanks to its voting feature.
It is easy to use - just login with GitHub.

Also, if this issue is a bug, please consider sending a PR with a fix. We rely on the community to provide
bugfixes as the core team is focused on performance.

@facebook facebook locked as resolved and limited conversation to collaborators Jul 22, 2018
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Jul 22, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

No branches or pull requests

4 participants