React Best Practices for Software Design and Architecture has been working as a React developer since 2018. To keep an app productive and flexible we have to follow the software's architecture and design. We have to work on it effectively and change it without rewriting its base code.

9m read timeFrom levelup.gitconnected.com
Post cover image
Table of contents
React Best Practices for Software Design and ArchitectureComponentsSweet Functional ComponentsWrite Consistent ComponentsNaming the ComponentsOrganizing Helper FunctionsNever Hardcode MarkupLength of the ComponentUse Comments in JSXDestructing of PropsQuantity of PropsPrefer Objects over PrimitivesNo More Nested Ternary OperatorsUse Separate Component for ListsWhen Destructuring Assign Default PropsNo More Nested Render FunctionsState ManagementUse ReducersFavor Hooks to HOCs and Render PropUtilize Data Fetching LibrariesState Management LibrariesSmart & DumbStateless & StatefulApplication structureCombine with Route/ModuleMake a common moduleMake use of Absolute PathEnfold External ComponentsShift Components in FoldersPerformanceDon’t Try To Optimize PrematurelyObserve The Bundle SizeTestingDon’t Depend on Snapshot TestsTest Correct RenderingCode Integration TestsStylingUtilize CSS-in-JSMaintain Styled Components TogetherBuy Me A Cup Of Coffee
5 Comments

Sort: