Disable ESLint "Quick Fix" suggestions in VSCode - visual-studio-code

I am using ESLint in my React project to format and lint my code. I use VSCode as editor, and I find the "Quick Fix" suggestions offered by VSCode quite handy, like "import module" etc. However, after enabling ESLint, the default Quick Fix suggestion of VSCode is replaced by ESLint's Quick Fix suggestions:
How do I disable this? Please note that I still want ESLint to format and fix my code, but I don't want its quick fix suggestions. Instead I want VSCode to show its original Quick Fix suggestions. Like in above case, I want VSCode to suggest importing Link from react-router-dom rather than ESlint offering me its own quick fix suggestions (this was happening before enabling ESLint).

I had a similar issue with bash scripts. Disabling the ShellCheck extension solved the issue for me.

Related

How to turn off prettier derived eslint errors in vscode?

I love what prettier does in tandem with eslint. I am glad that we can't push up misformatted code without errors, but is there a way to turn off the complaints in vscode? I don't need vscode giving things a red underline because I hit enter and now something is on a new line that the formatter doesn't like, especially when I have format on save. I would guess that the only solution to this is to remove all linting related to formatting and just have things fixed with the running of formatting in pre commit hooks and github actions...
To add onto this. I think the errors I'm getting come from this plugin included in .eslintrc:
"plugin:prettier/recommended"
When I turn it off the errors go away. My preference would be to find a way to hide these errors in vscode while keeping this plugin

VSCode Emmets missing

I deleted some extensions and after that my VSCode Emmet are not working as it used to be. I tried searching for solutions, which led me to going in my Extensions in Setting but the Emmet in extension are also missing. Does anyone know how to fix this?
In your Extensions searchbox input #builtin. Emmet should be listed in the Features category. Note that Emmet can be disabled from vscode but not uninstalled.
If your Emmet extension says it is disabled, then re-enable.

VSC Highlighting with Svelte

I have been trying out Svelte for the last couple of days.
Everything is working fine, but then for some reason I get those weird highlighting bugs in VSC.
Whenever that happens, VSC is basically no longer useable (No IntelliSense, weird Highlighting, ...)
Has anyone of you experienced similar problems with Svelte?
I recommend you update your IDE, your plugins and svelte if you haven’t already, to use the official Svelte plugin for VS code, to disable other plugins that may conflict with IntelliSense, and reloading VS Code. If the problem persists, it would be better to ask for help on the plugin’s Github page.

VS Code - command 'emmet.expandAbbreviation' not found

Emmet Abbreviations are not working for me in VS Code. I looked up solutions, and added "emmet.triggerExpansionOnTab": true to my settings.json file.
When I added it, every time I pressed tab to indent it says "command 'emmet.expandAbbreviation' not found".
It stops showing that once I remove the line.
Additionally, there is no syntax coloring or suggestions in HTML files. I tried to fix it by adding "files.associations": {"*.html": "html"} but that didn't work either.
Does anyone know how to fix this?
I had this issue too, but I simply restarted VS Code and that actually solved the problem!
I had the same issue as well and could not find much help.. but what fixed it for me was using a previous version.. so something with the never version might not work with my settings I guess (and some them I can't change like my Mac OS..;-).. as my mac is 2015 edition).. Anyways if you are still having this issue.. this link is what worked for me..
https://code.visualstudio.com/updates/v1_55
Download an earlier version and you should be fine...
I simply commented out "emmet.triggerExpansionOnTab": true then it started working.
After trying a lot of different things (including re-installing vscode) I got desperate, disabled all of my extensions, reloaded vscode, and then reinstalled my key extensions. I didn't figure out which extension may have been causing the problem, but that did get it working again.
I solved it by re-enabling the emmet extension again. Not sure when it has been disabled.
Open the built-in extensions explorer (direct command: Extensions: Show Built-in Extensions), scroll down to find the emmet extension. For me it was disabled, and I had to open the context menu and click Enabled.
I recently encountered this problem after a VS Code update. I searched for disabled extensions and saw that, to my surprise, some 2/3 of my extensions have been disabled. I manually enabled one which seems to have triggered something because within seconds all these extensions (except those I actually had disabled some time ago) were live again.

VS Code cursor jumping to bottom

Why does my cursor jump to the last line of code when I create new tags? For example, when I type a comment in HTML, as soon as I type the !, it jumps to the bottom. What setting do I have to change to prevent this from happening? It is very annoying. I am just starting to use VS Code so sorry if this is a really simple fix.
I had a similar issue. The Flow Language Support extension was causing it. I disabled it, and then the issue was gone.
I had the same issue when I first started using vscode.
Explanation
Generally, the issue is caused by an extension of some sort that is messing with your IDE. Like the extension is trying to do its job but either there is a conflict with other extensions or vscode settings or that's how it works.
More specifically, I found the issue was caused by the the HTML, CSS, JS formatter extension.
Solution
If you have that extension, try disabling it and restart vscode. if the issue is fixed then you may leave it disabled or uninstall it. If it is not solved repeat the process with other extensions, especially those that format your code, until you find the culprit and remove it.
Also i got this type of issue.The solution is just disable your auto save it will work.
If you're an Angular developer, maybe consider disabling Angular Essentials Extension by "John Papa". Then restart VS Code.
That worked for me after several frustrations.