It’s always returning exit code 0 - see the GitHub issue. Unfortunately there’s no way how to stop build if GoLint has any kind of objections. Program: full resolved path to golint ( $GOPATH/bin/golint).Mark all 4 option checkboxes enabled: Synchronize files after execution, Open console, Sow console when a message is printed to stdout/stderr.Before launch - Green plus - Run external tool - Green plus (just once, next time you’ll reuse if necessary).Run - Edit configurations - Defaults - Go application.The sooner you start with it, the nicer code you’ll produce. GoLint is a linter tool that will make you write and document your code properly. ![]() Enable and put a big number in Save files automatically if application is idle for X seconds (disabling this will cause autosave being triggered again).Enable save files on frame deactivation.Disable synchronize files on frame or editor tab activation.File - Settings - Appearance & Behavior - System settings.Disabling autosave is mandatory to be able to work with the GoImports. *Files are being altered by external tool and IDE would move the caret around every second because of autosave -> external change -> reload cycle. The problem here is that if autosave was trigerred every second, your caret would move around randomly all the time when GoImports is run and you would go nuts very quickly. We need to one more fix related to saving. Confirm (rest can be kept with default values)Īfter every save, GoImports will get triggered and your code will be formated and altered as necessary.Environment variables (skip if you’re not using Vendor experiment): GO15VENDOREXPERIMENT=1. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |