Can clicking "run tests" automatically save the file?

[skybrian]

If I edit a test and click "run test", there is a dialog:

File has unsaved changes. Save and try again.

It seems like it would be better to automatically save the file?

[skybrian]

In case it matters, I have file.autoSave on. Here are my preferences:

{
    "[plaintext]": {
        "editor.quickSuggestions": false,
        "editor.wordWrap": "bounded"
    },

    "editor.stablePeek": true,
    "files.autoSave": "onFocusChange",
    "go.coverageDecorator": "gutter",
    "go.coverageOptions": "showUncoveredCodeOnly",
    "go.inferGopath": true,
    "go.lintOnSave": "off",
    "go.toolsGopath": "/Users/skybrian/go/tools",
    "go.useCodeSnippetsOnFunctionSuggest": true
}

[ramya-rao-a]

Sure that is doable and is pretty simple.
PRs are welcome.

The change should be done here: https://github.com/Microsoft/vscode-go/blob/0.6.65/src/goTest.ts#L34

You can use editor.document.save() to save the document

[curiouslychase]

would it make sense to have this disabled by default and have a flag to enable? something like go.saveTestFileOnRun (alternatively to check if files.autoSave is onFocusChange)?

[ramya-rao-a]

@chaseadamsio Why so? When you explicitly click on the Run test code lens or use one of the test commands from the command palet, you are making a conscious decision to run the test and so saving the file makes sense. Am I missing something?

Is it so as to not race with the Auto Save feature?

[curiouslychase]

If the expected behavior is always save the file when you run the tests I think it makes sense. Personally I like having flags for anything I might want to disable, so that was the only reason I suggested it. I'll pick this up and submit a PR.

[ramya-rao-a]

In the latest update to the Go extension, the files get saved when test is triggered.
Thanks @chaseadamsio for the fix!