-
Notifications
You must be signed in to change notification settings - Fork 12
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
[Bug] VSCode Integration Not Working #40
Comments
Sounds like you might be running Prettier as a linter rule via ESLint and eslint-plugin-ember. If so, this sounds like ember-cli/eslint-plugin-ember#1659 |
Oh so is the issue that the error w/using eslint-plugin-prettier w/this plugin throws an error thats silently causing the red squiggles to not show? I can do |
Most likely this, yes. What happens when you try to run I think |
Oddly no... nfurniss: bs-proj (master) $ node_modules/eslint/bin/eslint.js app/components/test.gjs
/Users/nfurniss/code/bs-proj/app/components/test.gjs
1:7 error 'q' is assigned a value but never used no-unused-vars
1:1 error Replace `⏎` with `·` prettier/prettier
0:0 error Replace `__GLIMMER_TEMPLATE(`<Foo·/>"lol"`,·{·strictMode:·true,·scope:·()·=>·({Foo})·})]` with `⏎··__GLIMMER_TEMPLATE(`<Foo·/>"lol"`,·{⏎····strictMode:·true,⏎····scope:·()·=>·({·Foo·}),⏎··}),⏎]⏎` prettier/prettier
4:12 error 'Foo' is not defined no-undef |
Note that the |
Going to close this since it's roughly the same issue with the same solution as #20 |
🐞 Describe the Bug
VSCode is not showing Prettier errors in
gjs
files, but does injs
filesHowever, the prettier plugin is working, as it can be successfully invoked from the commandline:
🔬 Minimal Reproduction
Repro repo: nlfurniss/bs-proj@61a82ea
😕 Actual Behavior
No red squiggles in VSCode
🤔 Expected Behavior
Red squiggles in VSCode
🌍 Environment
➕ Additional Context
Installed VSCode plugins:
The text was updated successfully, but these errors were encountered: