-
Notifications
You must be signed in to change notification settings - Fork 646
0.6.71 rejects all changes, until goreturns is updated #1447
Comments
Do you see any errors in the console? Help -> Toggle Developer Tools -> Console
|
Does manual formatting remove the changes as well? |
Can you repro it if you added the setting |
I've got similar error. Somehow it solved after I install this package: |
Thanks @harunrzl. @ryantriangles Does that help you as well? |
Same problem (on Linux). |
Setting Invoking goreturns manually works fine, and doesn't remove the lines that it removes in vscode-go. Despite installing goreturns manually (with |
@ryantriangles Looks like the I am able to repro the issue by installing an older version of I have pushed a fix which you can try as well.
|
I've published a release that should fix this issue. Sorry for the trouble everyone. |
Now, code formatting never work☹ |
me too,the vscode formatting never work,I cannnot write code with the ide |
@zengming00 @wangjieyanda Which platform are you on? Windows? Mac? Linux? |
it was solved in 0.6.72 version,thanks @ramya-rao-a |
@ramya-rao-a The binary program of @zengming00 @wangjieyanda You can build the binary program of |
@WenhaiLin Do you get the pop up asking you to update |
@ramya-rao-a Yes, it happen time and time again. So I build the binary program of |
@WenhaiLin Then Try running it manually |
@ramya-rao-a @WenhaiLin |
The update to 0.6.71 has introduced a strange bug for me, which persists even despite uninstalling and re-installing the plugin: the formatting process rejects any and all changes, with the sole exception of defining the package name.
Any lines I add to a file will be erased the moment I save. Any lines I delete from a file will be restored the moment I hit save. It doesn't remove legitimate lines that were already there – if I write some code in vim, then open the file in VS Code and edit it, saving only removes the lines VS Code added. (It does still remove illegitimate lines, like an unused import.)
I don't have auto-save on, and I haven't customised any of VSCode-Go's settings.
The text was updated successfully, but these errors were encountered: