Hacker News Reader

Comment by skurfuerst | Hacker News Reader

Hey,

Thanks, you are right!

Do you have a good suggestion on a syntax how people could use the "debugger" in a nice way? I kinda dislike first creating a component and then wrapping it completely afterwards, although that of course would work.

All the best, Sebastian

View on HN

You could just imperatively instrument the component, e.g.:

    class MyComponent extends React.Component { /* ... */ }
    debugReasonForRendering(MyComponent);

Where `debugReasonForRendering` patches `arguments[0].prototype. shouldComponentUpdate`.

Since this is entirely for debugging purposes, I feel like the decorator is perfectly fine until the standard is complete. It's unobtrusive (i.e. no refactoring needed) and easy to remember. Maybe a warning inside the decorator is `process.env.NODE_ENV === "production"` warning would be nice.

Reply on news.ycombinator.com