• could utilize fzf
• cursor should jump to selected item (line) once chosen
• should match type and function/method definitions

Add a force option to goimports. It should write to the file after the formatting is done.

gotest output in case of failure seems to still be missing content. The helpful info is discarded.

godef! should respect current window layout (split vs vsplit).

Formatters (gofmt, goimports) should try to keep the cursor at or close to the position before the re-insertion of the formatted content.

Looks like the goswap command sometimes doesn't want to switch from the test file to the implementation file or the other way around.

Most probably that it's happening with long files/paths.

Extract some of the command code into separate functions and write unit tests for them. Take a look at the available Lua testing libraries.

Leave vis mocking for now, just the basic stuff.

Match the behaviour / implementation of the gout command (outline) to the one implemented in rokf/vis-fzf-outline. Mention that plugin as an alternative to the gout command.

Add a goimports command that pipes the current range through goimports.

It should have a configurable -local flag option (presumably through an environment variable - GOIMPORTS_LOCAL - to make it more convenient).

gotest should respect current layout (new vs vnew).

It should operate on the file buffer instead of a file (if possible), otherwise make sure that the file gets reloaded properly and on time.

It should run go test on the current file/package.

If the cursor is inside a test it should only run that test (utilize the force flag).

gout command errors when no option is chosen from the outline (format). This shouldn't happen.

Update the gotest command so that it runs a single test (the one the cursor is in?) in the presence of the force suffix (gotest!).

I've made some changes to the outline patterns that vis-fzf-outline contains for Go today.

Sync that with gout here once deemed stable. It might require some additional tweaks.

A forced (!) goswap could open the file in a new window. I usually split and swap anyway, to have both the implementation and test case side by side.

Try adding some Guru integration. Find out if there's anything that could be useful.

https://github.com/golang/tools/tree/master/cmd/guru