-
Notifications
You must be signed in to change notification settings - Fork 889
--project option outputs absolute paths #3183
Comments
I looked into this. When using Possible solution:
|
This absolute paths bug prevents from using tslint on VSCode running from a task, in the scenario where the tooling is ran in WSL and the editor in Windows. The output file paths are linux like paths, but the VSCode in Windows expects Windows formatted paths. |
@akaztp that's probably better fixed in the formatter. What formatter are you using? |
I solved my problem using a beta extension of tslint that uses the TypeScript language server plugin, so I don't need the output of the tslint as a task, anymore. |
💀 It's time! 💀TSLint is being deprecated and no longer accepting pull requests for major new changes or features. See #4534. 😱 If you'd like to see this change implemented, you have two choices:
👋 It was a pleasure open sourcing with you! If you believe this message was posted here in error, please comment so we can re-open the issue! |
🤖 Beep boop! 👉 TSLint is deprecated 👈 (#4534) and you should switch to typescript-eslint! 🤖 🔒 This issue is being locked to prevent further unnecessary discussions. Thank you! 👋 |
Bug Report
Actual behavior
tslint --project .
outputs absolute paths.Expected behavior
Since
--outputAbsolutePaths
is not used, tslint should print relative paths.The text was updated successfully, but these errors were encountered: