Skip to content
This repository has been archived by the owner on Nov 16, 2023. It is now read-only.

Make misconfigured TS lint more obvious #99

Closed
mjbvz opened this issue Jun 10, 2019 · 1 comment
Closed

Make misconfigured TS lint more obvious #99

mjbvz opened this issue Jun 10, 2019 · 1 comment
Assignees

Comments

@mjbvz
Copy link
Contributor

mjbvz commented Jun 10, 2019

Many users seem not to be getting this extension working. Although the feedback is vauge, we suspect the issue is that tslint is either not installed in a way we understand or misconfigured

We currently show a warning on the first line of every file you open if:

  • We cannot load tslint
  • And your workspace contains a tslint.json file.

We don't always want to show a warning if tslint cannot be found as as this would be annoying in workspaces that are not using tslint.

Some ideas on making this better:

  • Add warning icon in the status bar (like old tslint extension)
  • Show warning if the user is using a custom tslint.json path, such as tslint.dev.json
  • Add more documentation on investigating why the plugin may not be enabled
@mjbvz
Copy link
Contributor Author

mjbvz commented May 1, 2023

Closing as TSLint has been deprecated in favor of ESLint and this extension is no longer being maintained

Please look into migrating to use ESLint and the ESLint VS Code extension

@mjbvz mjbvz closed this as completed May 1, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant