Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
React Design Patterns and Best Practices

You're reading from   React Design Patterns and Best Practices Build easy to scale modular applications using the most powerful components and design patterns

Arrow left icon
Product type Paperback
Published in Jan 2017
Publisher Packt
ISBN-13 9781786464538
Length 318 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Michele Bertoli Michele Bertoli
Author Profile Icon Michele Bertoli
Michele Bertoli
Arrow right icon
View More author details
Toc

Table of Contents (13) Chapters Close

Preface 1. Everything You Should Know About React FREE CHAPTER 2. Clean Up Your Code 3. Create Truly Reusable Components 4. Compose All the Things 5. Proper Data Fetching 6. Write Code for the Browser 7. Make Your Components Look Beautiful 8. Server-Side Rendering for Fun and Profit 9. Improve the Performance of Your Applications 10. About Testing and Debugging 11. Anti-Patterns to Be Avoided 12. Next Steps

Inline styles


The official React documentation suggests developers use inline styles to style their React components. This seems odd, because we all learned in past years that separating the concerns is important and we should not mix markup and CSS.

React tries to change the concept of separation of concerns by moving it from separation of technologies to separation of components. Separating markup, styling, and logic into different files when they are tightly coupled and where cannot work one without the other is just an illusion. Even if it helps keep the project structure cleaner, it does not give any real benefit.

In React, we compose components to create applications where components are a fundamental unit of our structure. We should be able to move components across the application, and they should provide the same result regarding both logic and UI, no matter where they get rendered.

This is one of the reasons why co-locating the styles within our components and applying them using...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image