You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Do you want to request a feature or report a bug?
Request a feature
What is the current behavior?
React prop types warning doesn't reveal info on the component's instance
What is the expected behavior?
Print also the component's props
Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?
N/A
The current warnings point the developer only to the source code, and it would be AMAZING if we'll easily see which component instance caused the warnings. Consider a list with hundreds of items, each rendering a component. ATM there's no convenient way to track down the renegade instance.
So instead of the current behavior:
Also add:
index.js:1375 Warning: Failed prop type: The prop `latitude` is marked as required in `RestaurantListItem`, but its value is `null`.
RestaurantListItem's instance has the following props: {OBJECT_OF_PROPS_THAT_OPENS_ON_CLICK}
I currently find myself many times having to temporary do this in different components.
It seems to me like a very easy thing to add, at least for development build.
Thoughts?
I can take a swing at it with some guidance (I'd love to dip my toes in React's code)
The text was updated successfully, but these errors were encountered:
Do you want to request a feature or report a bug?
Request a feature
What is the current behavior?
React prop types warning doesn't reveal info on the component's instance
What is the expected behavior?
Print also the component's props
Which versions of React, and which browser / OS are affected by this issue? Did this work in previous versions of React?
N/A
The current warnings point the developer only to the source code, and it would be AMAZING if we'll easily see which component instance caused the warnings. Consider a list with hundreds of items, each rendering a component. ATM there's no convenient way to track down the renegade instance.
So instead of the current behavior:
Also add:
I currently find myself many times having to temporary do this in different components.
It seems to me like a very easy thing to add, at least for development build.
Thoughts?
I can take a swing at it with some guidance (I'd love to dip my toes in React's code)
The text was updated successfully, but these errors were encountered: