What is the expected output for the assignment on line template.go/229 ? I'm not sure how we can add tags here (but maybe I'm missing something). For the record, here are some examples that we support recently: https://github.com/fatih/gomodifytags/releases/tag/v1.13.0

Based on the title, it sounds like the feature is about transformation to use named fields instead of positional args for struct literals. gomodifytags is to add structure tags, so unrelated.

Yes, @hyangah has the right intent.

I want the code action to transform the code from

	 ret := &Template{ 
	 	nil, 
	 	text, 
	 	text.Tree, 
	 	t.nameSpace, 
	 } 

to

	 ret := &Template{ 
	 	escapeErr: nil, 
	 	text:      text, 
	 	Tree:      text.Tree, 
	 	nameSpace: t.nameSpace, 
	 } 

Aha I see, thanks for the clarification. I think keyify does this for you (it also has an emacs plugin). In vim-go you can use :GoKeyify

https://github.com/dominikh/go-tools/tree/master/cmd/keyify

Integrating keyify with gopls is on my todo list. At the same time, gopls already has fillstruct, and I wouldn't be surprised if most of the code required for keyify and fillstruct is identical.

It seems that it's not easy to get keyify to work with Go modules these days: dominikh/go-tools#834

And although golang/vscode-go#1631 has been resolved, which seems to have made omitting field names a better option, I think having field names still has its advantages:

• Easier when adding/removing fields. Especially helpful in tests where test structs often have consecutive fields of the same type
• Still in tests, sometimes we write a bunch of new tests that have field names and now we'd like to add field names to the existing ones
• As a neovim user I'm still waiting for anticonceal (virtual text occupying horizontal space) neovim/neovim#9496

So it'd be great if gopls can offer this functionality.

This capability has been available since gopls@v0.9.0 and works in neovim lsp too

This issue can probably be closed as a dupe of #53062 which has the attached PR that was merged in v0.9.0 to support this capability

Thank you for spotting that, @dnwe!

@dnwe Looks like this only works if the struct is in a different package?

No code actions on Bar (or govet warning)

Foo on the other hand:

Our test matrices usually involve some (anonymous) structs in the same package. Any way to make this case work? Ty