ESLint 7.0
eslint.org
ESLint 7.0
1–10 of 93 posts
Re: ESLint 7.0
#2Re: ESLint 7.0
#3However, I confess that after adopting ESLint in my workflow, things have improved considerably. I can ask it to warn me on unused stuff, to enforce the lack of semicolons, to format and indent my code correctly on save... it's a very useful tool. If you have something against JavaScript in general, give it a try.
Re: ESLint 7.0
#4Re: ESLint 7.0
#5I haven't done TypeScript/JavaScript in a while. What's the status of ESLint taking over from TSLint (for both the tool itself and the vscode extensions)?
https://github.com/typescript-eslint/typescript-eslint
Haven't ran into too many issues within the last 8 months or so. Only in Spring 2019 was it bad IME.
Re: ESLint 7.0
#6I haven't done TypeScript/JavaScript in a while. What's the status of ESLint taking over from TSLint (for both the tool itself and the vscode extensions)?
Re: ESLint 7.0
#7Please use that rule. So many bugs in the JS world is because of dangling promises.
Re: ESLint 7.0
#8There is a rule in eslint that warns you when a promise is dangling and hasn't been handled. Please use that rule . So many bugs in the JS world is because of dangling promises.
Re: ESLint 7.0
#9There is a rule in eslint that warns you when a promise is dangling and hasn't been handled. Please use that rule . So many bugs in the JS world is because of dangling promises.
hundreds of rules to read, is this on its recommended list if it's so critical? is its name 'no-floating-promises'?
Yes, and I subscribe to the parent's sentiment: this rule is essential
Re: ESLint 7.0
#10 // eslint-disable-next-line no-console -- Here's a description about why this configuration is necessary.
console.log('hello');
https://eslint.org/docs/user-guide/configuring#disabling-rul...