Closed ManAnRuck closed 4 years ago
no pr for this.
just check if ESLint works fine in viscose (no warnings thrown in Output > ESLint) yarn lint command works without an error
@ManAnRuck Which repository is affected by this? Clinet only?
Then i guess we can close this -> Travis does the check, right?
no, currently travis does not check this
Works fine. One question tho:
The command eslint 'src/**/*.{ts,tsx,js,jsx}' --fix
is executed apparently - should we run a --fix
on every occasion? Shouldnt that be the job of the developer?
yes I would do it. less work when there is for example just a space missing. let the machines let do the work if the developer forget something ;)
The problem is, that travis will always be successful if using yarn lint
since it will fix all the errors present in the repo on the fly.
I suggest: Remove the --fix
flag. It would be totaly fine to use a developer shortcut for linting like yarn devlint
or similar, which uses the fix flag
it's not possible to commit something with lint errors. so this would not be the case. (if you ignore the commit hook, and travis will make this job, and there is only a auto fixable issue, travis will commit this)
change eslint/typescript linting & prettifier packages to use newer typescript version https://dev.to/thefinnomenon/react-native-linting-testing-15gf
@react-native-community/eslint-config is not really good maintained