Age | Commit message (Collapse) | Author | |
---|---|---|---|
2020-08-28 | #3325 - ale#path#BufferCdString now generates %s:h | w0rp | |
2019-07-01 | Support $GO111MODULE with Go tooling | Elias Martinez Cohen | |
Allows the user to override $GO111MODULE environment variable through ale options. This gives control over the default behavior of Go module resolution. Golang documentation: https://github.com/golang/go/wiki/Modules#how-to-use-modules Add `ale#Go#EnvString()` function to make it easy to add similar Go environment variables in the future. Use the new `EnvString` function in all available Go tools callbacks & update tests Also add test of linter command callback for `gofmt` | |||
2019-04-07 | #2132 - Replace command_chain and chain_with with ale#command#Run | w0rp | |
2018-10-23 | ale#path#CdString include ale#Escape | paihu | |
2018-10-22 | fix testcase | paihu | |
2018-09-19 | Add fixer for Go modules (#1873) | Martin Tournoij | |
* Add fixer for Go modules | |||
2018-08-23 | Remove "go env" from gobuild linter | Martin Tournoij | |
I see no reason to do this? It is just setting the environment to what it already is? It was originally added in #297, but that entire PR is not a great idea in the first place; that PR (together with #270) tried to make the Go do non-standard and non-supported stuff like compiling packages outside of GOPATH. That's not something that works well (I tried), so was eventually removed in #465, but these "go env" calls remained, for no reason in particular, as far as I can think of. This will improve on #1834; you will now no longer get a confusing error (but still won't get a meaningful error; need to think how to do that). | |||
2018-07-15 | Massively reduce the amount of code needed for linter tests | w0rp | |
2018-02-04 | #1206 Add support for setting options for gobuild, and escape paths better | w0rp | |