Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"tslint.configFile" absolute file path required with VSCode #298

Open
joelricci opened this issue Aug 26, 2019 · 3 comments
Open

"tslint.configFile" absolute file path required with VSCode #298

joelricci opened this issue Aug 26, 2019 · 3 comments

Comments

@joelricci
Copy link

I'm not sure if this issue is more related to VSCode, tslint or this plugin, but considering that tslint works as expected except for the prettier part I'm starting by posting an issue here.

My project folder structure looks similar to this:

<root>
├── backend
└── frontend
    ├── tslint.js
    └── .prettierrc

In VSCode, I open the project root. Now prettier won't do anything unless I specify an absolute path to the tslint.js file for "tslint.configFile" config option in VSCode.

OS: macOS 10.14.6
VSCode 1.37
tslint@5.14.0
tslint-plugin-prettier@2.0.1

tslint.js:

module.exports = {
    extends: [
        'tslint-plugin-prettier',
        'tslint-config-prettier',
    ],
    rules: {
        'prettier': true
    }
}
@ikatyang
Copy link
Member

I'm not sure but I guess this is an issue for the TSLint VSCode extension. Could you provide some logs from your TSLint VSCode extension (the TSLint section in the Output panel) so that we could investigate?

@joelricci
Copy link
Author

joelricci commented Aug 28, 2019

Could you provide some logs from your TSLint VSCode extension (the TSLint section in the Output panel) so that we could investigate?

Thanks for looking into this. I don't seem to have a TSLint section in the output panel though. Or do you mean TypeScript ?

image

@ikatyang
Copy link
Member

I thought you're using the first one, but it seems it's the third one:

Do you have a repro repo that I can simply clone it and reproduce the bug?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants