Container/Presentational Pattern
patterns.dev · 1,324 words · saved by 1 readers
Enforce separation of concerns by separating the view from the application logic
In 2015, Dan Abramov wrote an article titled “Presentational and Container Components” that changed the way many developers thought about component architecture in React. He introduced a pattern that separated components into two categories: Presentational Components (or Dumb Components) : These are concerned with how things look. They don’t specify how the data is loaded or mutated but rather receive data and callbacks exclusively via props. Container Components (or Smart Components) : These are concerned with how things work. They provide the data and behavior to presentational or other cont
saved by
related reading
- Container/Presentational Patternpatterns.dev
- Tao of React - Software Design, Architecture & Best Practices | Alex Kondovalexkondov.com
- Building Bulletproof React Components - Shu Dingshud.in
- Blogged Answers: A (Mostly) Complete Guide to React Rendering Behavior · Mark's Dev Blogblog.isquaredsoftware.com
- You Might Not Need an Effect – Reactreact.dev
- What will you ship?rauno.me
- Modularizing React Applications with Established UI Patternsmartinfowler.com
- Building data-centric apps with a reactive relational databaseriffle.systems
- SWR: React Hooks for Data Fetching - Vercelswr.vercel.app
- Pure UIrauchg.com
- Redux Essentials, Part 1: Redux Overview and Concepts | Reduxredux.js.org
- srclsacred.computer