In part one we talked about Monolithic Components and a Lack of Abstraction. In this post, we will continue talking about best practices we’ve found working with React/Redux over the past year. Connecting too many components is an issue that should be avoided when working in React and Redux. Having too many components connected to […]
Following best practices ensures your application is in the best possible position to live a long healthy life. Some frameworks come with a strong set of opinions that shape best practices. React, however, is very new and very much a library, not a framework. As such, its best practices are still taking shape. In the […]
With all of the craze in web development around React and Redux currently, we at PMG started using it about a year ago and have adopted it in most of our tools that run in the browser. It has made working with Javascript and the presentation layer much more enjoyable than what has been done […]
Yesterday while reviewing a few pull requests from my coworkers, I was struck by how easy a few changes were in some React code. The changes were easy because the codebase in question had found the right level of abstraction in the pieces that were changing. ReactJS may be the next shiny new thing, but […]
React, a framework for the view part of your JS application, doesn’t supply two way data binding by default. It expects that your data flows downward from your model (whatever that is) to the view (react component). So say you want part of a form field to update another part of an application: you’ll have […]