Twitter | Search | |
Ryan Florence 20 Feb 18
Your periodic reminder to turn off linting rules (or start a programmer fight with your "senior developer" who turned it on) that make this kind of JSX impossible:
Reply Retweet Like
Ryan Florence
And really I'm saying get rid of the airbnb lint config. Use Prettier Use ESLint Config React App And then get stuff done with just the right amount of help from tools.
ESLint configuration used by Create React App
Reply Retweet Like More
sharno 🐌 20 Feb 18
Replying to @ryanflorence
Have been using this combination for a few months now and it's great. Along with Flow and Flow's linting rules, the code seems to be in a good shape (not perfect though)
Reply Retweet Like
Ryan Florence 20 Feb 18
Replying to @sharno3
💃🏼no such thing as perfect code
Reply Retweet Like
That’s not Alan, it’s Steve 20 Feb 18
Replying to @ryanflorence
it seems like there’s an unfilled need for a no-style-rules eslint config. Turn on as many bug-preventing rules as possible, but leave stylistic preferences open. Would pair really well with Prettier
Reply Retweet Like
Ryan Florence 20 Feb 18
Replying to @stalefries
that's react-app for me.
Reply Retweet Like
Tycho Tatitscheff 20 Feb 18
Expo did make eslint-config-universe which is stricter than cra but loosy enough on style rules to let prettier works. Highly recommend it.
Reply Retweet Like
Matteo 20 Feb 18
Replying to @ryanflorence
I totally agree. Prettier + eslint-config-react-app is more then enough for smaller teams. Shameful plug: we use , which is eslint-config-react-app without the need of the external peerDependencies.
Reply Retweet Like
P1xt 20 Feb 18
Replying to @ryanflorence
But, if I use Prettier with ESLint and the airbnb rules - my code doesn't get all crapped up with nested ternaries. 😀
Reply Retweet Like
K 21 Feb 18
Replying to @ryanflorence
Does this work out of the box with React-Native?
Reply Retweet Like