A blog post I want to see: Setting Up CSS-First People for Success in a JS Codebase Talking about friendly tooling, reasonable lint rules, documented workflows, and support resources.
-
Show this thread
-
There are some barriers that aren’t obvious to some engineers. Such as if you don’t allow sending code for review with lint warnings, you’re setting up designers for failure. Same for if you don’t document a few wiki pages with examples of common changes.
8 replies 5 retweets 63 likesShow this thread -
Replying to @dan_abramov
A first step that might help with that here would be a pre-commit hook that will lint the file automatically without the designer needing to do anything.
1 reply 0 retweets 0 likes -
Replying to @mkupsmth
I think that commit hooks actually create problems because they don’t let you submit WIP code for help when you’re stuck. You can’t get it off your computer.
6 replies 1 retweet 3 likes
Analogous to this but I feel the same way about type-checking blocking code from being transpiled and executed. Type-checking should not block the execution of your code. Linting should not block the code review process.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.