gci error not clear about gci

[ngehrsitz]

@georgettica The error reporting in gci is an area that could definitely improved. Until that happens I would recommend that you run gci in write mode to see what output gci expects.

[KenjiTakahashi]

I've just added gci to my golangci-lint config and immediately got a bunch of errors like this:

Expected 'u', Found '"' at user.go[line 27,col 2]

Expected 'g', Found 'b' at processor.go[line 9,col 3]

Expected '"', Found 's' at main.go[line 10,col 2]

Etc.

It could really use a more readable error message, at first I thought the integration is just broken.

[georgettica]

I can also say rust is doing this very good for semicolon position.
It literally shows in the error message where you should add it

[daixiang0]

You can try latest version :)

[georgettica]

I will do that soon and report back, thanks!