It's very common to find best practices in programming, patterns, and guidelines on how to build things, how to behave, and so on. All of that is great, but what about bad practices? We often do something that isn't great and don't even realize it — who's going to tell us it's wrong, right?
Hey young grasshoppers! As I mentioned in another article, today I'm going to dive a little deeper into this wonderful library that is Styled Components. I'll split this topic into three articles: in this one I'll cover some of styled's features, in the second I'll talk about testing (don't take this order into account when building an application), and in the last one I'll explain best development practices (focused on styled components, of course).
Creating CSS with JS ò.ó
Well, this is my first article and I'm very excited about it. The person who encouraged me to write it was my friend Isac, I hope you enjoy it =D
Something I really love is CSS — I have a lot of fun with it, but not everything is perfect… There are moments when everything seems to fall apart: you fix something on one side and break it on the other.
It is very easy to create side effects with CSS, to override attribute values and classes, to break entire pages with a simple change of a few values.