4 ms·
Out of curiosity: how do you set up your CI checks (linter, formatting) if the opensource tools behave differently from JetBrains'? Do you use Qodana[0]? One b
by pzmarzly 1y ago
Out of curiosity: how do you set up your CI checks (linter, formatting) if the opensource tools behave differently from JetBrains'? Do you use Qodana[0]?
One benefit of using VSCode/Sublime Text/vim/emacs language integrations is that I roughly know what command to run to get the same results in the terminal as I get in the editor. With JetBrains does-it--all IDEs, I have no clue.
[0] https://www.jetbrains.com/help/qodana/getting-started.html https://www.jetbrains.com/help/qodana/getting-started.html
- jrockway 1y agoAs far as I went with linting this sort of thing was to check that "gofmt -s" yields the code that's checked in. https://github.com/pachyderm/pachyderm/blob/master/src/internal/analyzers/gofmt/gofmt.go https://github.com/pachyderm/pachyderm/blob/master/src/inter... It does not care if the imports are organized differently. I like to do: import ( # standard libraries "fmt" "io" # our stuff "github.com/pachyderm/pachyderm/src/internal/whatever" # packages "example.com/foo/bar" "github.com/whatever/whatever/foo" ) People/tools will remove the newlines or mix in local packages with upstream packages, and I decided not to care. I'm pretty sure nobody else cares.