Devin Rhode
Devin Rhode
Maybe a totally different approach would be to try and bake these rules directly into prettier. I think it _might_ start to break prettier's philosophy, but, the options could be...
Turns out that even stacking eslint on top of prettier, eslint does not know how to even maintain prettier's formatting: I tried to get eslint and prettier to play nice...
I think I found another rule that can cause problems: > getInitialState is a React lifecycle method, and should not be an arrow function or in a class field. Use...
Produces this code: ```tsx export default class Root extends Component { getInitialState() { return { errorImporting: null, errorParsing: null, errorUploading: null, file: null, fromExtension: false, importSuccess: false, isImporting: false, isParsing:...
Probably this is what it _should_ produce: ```tsx export default class Root extends Component { getInitialState() { return { errorImporting: null, errorParsing: null, errorUploading: null, file: null, fromExtension: false, importSuccess:...
yeah it actually seems totally unrelated to prettier. Tried disabling all the prettier stuff, run just eslint autofix, and still happening.
input: ```tsx export default class Root extends Component { getInitialState = () => ({ errorImporting: null, errorParsing: null, errorUploading: null, file: null, fromExtension: false, importSuccess: false, isImporting: false, isParsing: false,...
THANK YOU @ljharb this was driving me bonkers, I was convinced it was a bug related to prettier/eslint integration, but it seems isolated to eslint.
I've found in this situation where you are exclusively working on some `./node_modules/.bin/{foo,bar}`, `npm link` (6/7/?) works better than yalc. One reason I say this is that I found yalc...