Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

List of "rules do not yet have ESLint equivalents" is hard to find

See original GitHub issue

🚀 Feature Request

The console output ? 1 ESLint rule behaves differently from their TSLint counterparts: ? has a listing about all the rules with problems: * no-invalid-this: for example. So it is surprising that the part 5 rules do not yet have ESLint equivalents does not list the rules here, too. I think the easiest way (with not too much console output) is to add an hint about the log in current directory.

Existing Behavior

? 25 rules replaced with their ESLint equivalents. ?
? 1 ESLint rule behaves differently from their TSLint counterparts: ?
* no-invalid-this:
  - Functions in methods will no longer be ignored.
?? 5 rules do not yet have ESLint equivalents; defaulting to eslint-plugin-tslint. ?
? All is well! ?

Which 5 rules? I needed a few minutes to check if there is a log.

Change Proposal

? 25 rules replaced with their ESLint equivalents. ?
? 1 ESLint rule behaves differently from their TSLint counterparts: ?
* no-invalid-this:
  - Functions in methods will no longer be ignored.
?? 5 rules do not yet have ESLint equivalents (see generated log file); defaulting to eslint-plugin-tslint for this rules. 
? All is well! ?

Issue Analytics

State:
Created 4 years ago
Comments:6 (5 by maintainers)

Top GitHub Comments

2reactions

HolgerJeromincommented, Oct 11, 2019

I added an PR for the wording update. It does not close this issue in the case you want to implement the new sorting of tslint config in generated output. (which is for me out of scope of the time I can invest here)

1reaction

JoshuaKGoldbergcommented, Apr 26, 2020

Thought about this a bit - I think now that the CLI output is more clear (as @HolgerJeromin mentioned & improved), there’s not much more actionable here. A roadmap already exists in eslint-plugin that shows rule equivalents. Putting a visualization of that in the CLI, for example, is probably out of scope for what we really need to do.

Please do post here or open a new issue if you feel there’s more to be addressed!

Top Results From Across the Web

Migrating to v8.0.0 - ESLint - Pluggable JavaScript Linter

In ESLint v8.0.0 (via Acorn v8.0.0), the key and value are now separate objects and therefore no longer equivalent. To address: If your...

ESLint - npm

Hooks FAQ - React

There are no Hook equivalents to the uncommon getSnapshotBeforeUpdate , getDerivedStateFromError and componentDidCatch lifecycles yet, but we plan to add ...

What if ESLint's configuration worked like elm-review?

I was curious to see how the configuration for ESLint would look like ... already familiar with, and not a new DSL that...

Migrating and configuring Eslint with Angular 11

If you already had customized your TSlint rules, then the schematics should have taken care of converting them to ESLint equivalents.