I'm still working on it, but I think I've made good progress.

Still, nothing is breaking.

My primary goal is to enhance the project's maintainability, as this type of project can be challenging to maintain.

Project Structure

I reorganized the project into packages.
First, because we need it for golangci-lint.
Second, because it will be easier to maintain.

I replacedlogrus withslog (the logger is only used for debugging).

I still haven't decided if I will convert theshortener package to a module (to avoid some dependencies when using it as a lib)

Tests

I added a new test system that allows testing all theShortener options.
And so I added more tests.

I also added more tests on each structure, function, etc.

CLI Performance

I improved the performance of the CLI significantly by using the same design asgo fmt, and some optimizations.

My fork is about nine to fourteen times faster than the current golines.

Note: I don't have a recent laptop (~4 years old).

On the Kubernetes codebase:

It is not possible to usegofmt as CLI with the current official version.

Skip cases

I added more skip cases (testdata, dot directories, etc), basically the same thing asgolangci-lint fmt.

Bugs

I fixed some bugs:

• wrong directive pattern
• struct tag literals
• etc.

Notes

The default base formatter (goimports) didn't provide a good experience by default.
It was four times slower thangofmt.

I analyzed all the open issues and PRs of golines.

I fixed all the bugs inside the fork.

I'm thinking about how to proceed.

I think I will:

1. create a branchmain based on the currentmaster branch of the Segment repo.
2. switch the default branch of the fork tomain (instead offork as currently)
3. open a PR with all my changes and merge it. Not to be reviewed, but for history.
4. open an issue in the Segment repo.
5. wait for feedback from Segment before creating a tag