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

Stylelint doesn't work in .ts file #85130

Closed
daviddelusenet opened this issue Nov 19, 2019 · 6 comments
Closed

Stylelint doesn't work in .ts file #85130

daviddelusenet opened this issue Nov 19, 2019 · 6 comments
Labels
*caused-by-extension Issue identified to be caused by an extension

Comments

@daviddelusenet
Copy link

  • VSCode Version: 1.40.1
  • OS Version: macOS 10.15.1

Steps to Reproduce:

I'm setting up a new project with React, Styled Components and TypeScript. I've already done this before and I'm basically reusing the exact same setup.

However, in my new project the VS Code Stylelint extension doesn't work in .ts/.tsx files. It does work in .js files.

I'm using the same versions of everything and the exact same configuration. Some screenshots will follow now.

Working example of Stylelint in a .js file:

Screenshot 2019-11-19 at 15 51 18

Not working in a .ts file:

Screenshot 2019-11-19 at 15 51 32

Exactly the same setup in another project, there it does work:

Screenshot 2019-11-19 at 15 54 07

Please let me know if you need any more information, would love to provide it. This is driving me totally crazy.

@egamma
Copy link
Member

egamma commented Nov 19, 2019

Please file the issue against the StyleLint extension.

@egamma egamma closed this as completed Nov 19, 2019
@egamma egamma added the *caused-by-extension Issue identified to be caused by an extension label Nov 19, 2019
@daviddelusenet
Copy link
Author

daviddelusenet commented Nov 19, 2019

I'm not sure why you close this issue @egamma.

If everything is exactly the same in both projects but in one it works and in the other it doesn't, how can you be so sure that it's the plugins fault instead of VS Code itself?

@daviddelusenet
Copy link
Author

@egamma
Copy link
Member

egamma commented Nov 20, 2019

@davidbailey00

I'm not sure why you close this issue @egamma.

The issue cannot be reproduced given the steps you have provided in VS Code with all extensions disabled. Therefore the suggestion is to file the issue against the involved extension first.

@valin4tor
Copy link
Contributor

@davidbailey00

I'm not sure why you close this issue @egamma.

I think you meant to tag @daviddelusenet?

@daviddelusenet
Copy link
Author

Oh well, the author has deleted the extension.....

@vscodebot vscodebot bot locked and limited conversation to collaborators Jan 6, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*caused-by-extension Issue identified to be caused by an extension
Projects
None yet
Development

No branches or pull requests

3 participants