|
|
|
|
|
by picardo
4173 days ago
|
|
You're right about the boilerplate. I use a wrapper around React.createClass to take care of that. Kinda similar to Marty.createStateMixin, but it's just a component factory. The Chrome plugin looks very nice, but you can do the same thing with console.log() outputs in your store. It's a nice to have, but not filling a need for me. |
|
by that logic, you don't need a debugger with breakpoints and stack traces either.
i mean... you could use a spoon for driving nails into wood instead of a hammer, too.