@metalsadman yea can be a possibility but afaik new lint doesn’t support autoFixOnSave
maybe happen to you when you install all the extensions listed in quasar vscode page. then you can always try the above solution, it should work.
Latest posts made by jeevanjotsingh
-
RE: VS Code Config Problem In Boot File
-
RE: VS Code Config Problem In Boot File
I haven’t checked this with prettier, Uninstalled it first so I can use old settings and it worked but should remove
autoFixOnSave
first and usecodeActionsOnSave
. -
RE: VS Code Config Problem In Boot File
@metalsadman @Hawkeye64 @s-molinari I opened the pull request for the
New Settings
that worked for me, AutoFixOnSave should be replaced with this… -
RE: VS Code Config Problem In Boot File
@metalsadman pretty much I tried with both separately, I think the problem might occur with you as well, Just try to go to boot file and hit save, It might add a comma at last but such thing don’t work with other normal functions, But I will try to uninstall prettier and use the eslint simple.
-
RE: VS Code Config Problem In Boot File
@Hawkeye64 yes I tried it and Editor autoFixOnSave is now deprecated and not working after installing all extensions there and putting all into settings JSON
@s-molinari I think you are pointing toauto format on save
but when I turn it off for Editor it started following other save and format rules. -
VS Code Config Problem In Boot File
Hello Quasar
After following this withprettier
https://quasar.dev/start/vs-code-configurationMy Quasar boot file adds semicolon at the end of the function after each saves. Thank you.