
Dynamic Child Components with React
I’d like to suggest a simple piece of advice to fellow React devs out there. When rendering dynamic arrays of child elements within a React component…
Don’t Forget Your Keys!
I’d like to suggest a simple piece of advice to fellow React devs out there. When rendering dynamic arrays of child elements within a React component…
Don’t Forget Your Keys!
We work with our customers and partners to define project goals and objectives from a high level. Then we design and build. Then we release a thing and we start over. There is no point in detailing specifics on how we achieve our collective goals and objectives at the beginning of a project.
Ampersands can handle situations like reverse nesting, extending class and id names, and even adjacent sibling selection.
Concerns are modules you can use to extract code out of models and controllers. This is useful for various reasons. An obvious one is that this makes things skinnier, which we’ve already established is good. Another is that you can use these concerns to mix into other models and controllers
While it is definitely good to have a slim controller for sake of code reusability, readability, and testing, it is also good to have a skinny model (for the exact same reasons). In fact, its just good to have a skinny everything.