dan
If we remove the suggestion, it feels like we should also reopen that issue since it was a very popular request, and now it has no solution... I wonder if...
>I think that specifying some other global boolean (that DevTools and React both could read and respect) feels less fragile than encouraging people to override the hook. 👍
For now we'd rather not allow it because it makes it too easy to swallow errors (such as if the error boundary itself is buggy).
Now that I looked at this again, *the update codepath was already broken*. This just made the initial code path match it. So this is actually an improvement. We should...
I think the issue still exists, it’s just more consistent now
Feel free to grab it. I don't know if it's fixed or not but it's worth checking.
Can somebody please update the attribute table? https://github.com/facebook/react/tree/master/fixtures/attribute-behavior Run the fixture, save the Markdown file and put it in the same folder.
I think the pattern is not valid in general. Lazy should always either be hoisted to the top level of your file or cached outside of React. I understand the...