Conflict Between GCI and VSCode Go Extension: Blank Line Handling in Import Groups

[nicanorflavier]

Issue:

gci does not allow a blank line between external and local module packages, which conflicts with VSCode's Go extension. The Go extension automatically adds a blank line between different groups of imports (e.g., external and local module packages) for readability. As a result, gci reports that the blank line should be removed, while the Go extension insists on adding it back, causing a conflict between the two tools.

What version of GCI are you using?

gci version 0.13.4

Reproduce Steps

1. Create Go imports with external and local module packages, e.g.:

import (
	"github.com/labstack/echo/v4"
	"go.uber.org/zap"
	"mymicroservice_service/internal/config"
)

2. Run gci list or gci diff – it passes.
3. Open the file in VSCode with the Go extension installed.
4. Save the file (CTRL+S) – the Go extension adds a blank line between the import groups.
5. Run gci list or gci diff again – it fails, asking you to remove the blank line.

Open this in Visual

What did you expect to see?

gci should align with developer workflows and the Go extension's formatting by allowing the blank line between different import groups.

What did you see instead?

gci asks to remove the blank line between external and local module package imports.

[daixiang0]

I guess you do not set the import group, you can read the readme to set the group then vscode extension would not add blank.

[nicanorflavier]

I guess you do not set the import group, you can read the readme to set the group then vscode extension would not add blank.

You suggesting a fix that is not by default in vscode go extension rather than fixing this in gci to accomodate the developers workflow. Up to you, but I believe the devs would likely just disable this in .golangciyml if this is how you wanted it to be.