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
The proper way to handle this is not to pass the entire props object around. It's not practical or often possible for the plugin to follow references, and the only thing that should get a props object is an element.
In other words, pull status out prior to passing it to the function.
I ran your latest test case in a PR where we fixed the following issue: #1183 - and in there the test case passed! Prior to the changes from that specific PR, the test case was failing.
Removing the .map() code in the render() would make the component valid under the current implementation.
So I am quite confident those changes are also fixing the issue that you see here. And yes I would think that this to be a bug. Do others agree?
Activity
ljharb commentedon Mar 31, 2017
The proper way to handle this is not to pass the entire props object around. It's not practical or often possible for the plugin to follow references, and the only thing that should get a props object is an element.
In other words, pull
status
out prior to passing it to the function.MethodenMann commentedon Apr 3, 2017
ok i dont have exactly the same situation. This is my simplified component:
And i get the following linting error:
I figured out its because of the map. It this by design?
jseminck commentedon May 24, 2017
Hello,
I ran your latest test case in a PR where we fixed the following issue: #1183 - and in there the test case passed! Prior to the changes from that specific PR, the test case was failing.
Removing the
.map()
code in therender()
would make the component valid under the current implementation.So I am quite confident those changes are also fixing the issue that you see here. And yes I would think that this to be a bug. Do others agree?
42 remaining items