Case cannot be changed without removing tags first about gomodifytags HOT 3 CLOSED

Now that I see this, I know why I made it like this. Because sometimes the field names and the tag names might not the same. So you don't want to change existing keys, if they are there. When I started using this privately for couple of weeks I was annoyed of that. That's the reason it's enabled and I've added a comment that we should add a --override flag.

from gomodifytags.

Thanks @zmb3. I'll look into this.

from gomodifytags.

Hey @fatih - it's a pretty easy fix (see https://github.com/zmb3/gomodifytags/commit/9cc0c1fa6d114698a592109f663b72b095e19032), but it seems you intentionally didn't code it up this way as there's a test (which is now broken) to make sure we leave existing tags alone.

Do we really need an -override flag? This may make it more difficult for editors to integrate.

My opinion is that it's fine to overwrite existing tags. In most cases, people will be using this with structs that don't have any field tags. And in cases where they do have existing tags that they want to leave alone, they can use the -line option to exclude those lines.

from gomodifytags.