Closed pvalentim closed 8 years ago
Seems like it would be okay. React support built-in, TypeScript support via standardts
. I'll give it a go!
I think it may make more sense to use this: https://github.com/feross/eslint-config-standard
That way we're sticking with ESLint and can swap configs more easily in the future should we desire, plus altering it at all would be easier. Besides, we'd need the Babel ESLint parser for Standard anyway.
Immediate benefit: Right now by default the standard config forces single quotes in React JSX. Almost all convention says that React should use double quotes a la HTML/XML etc. This is easily overridden with the above. 👍
http://standardjs.com/
Any reason this wouldn't work with our setup ?