Inputs/Outputs best practice or naming convention

[alexanderilyin]

My current approach is to have inputs.go to store "inputs" and same with outputs.go, for example:

inputs.go

type SearchSomeService struct {
	Body struct {
		Search string `json:"search"`
	}
}

outputs.go

type SearchSomeService struct {
	Body struct {
		Data string `json:"data"`
	}
}

Problem is that mapRegistry panics with:

panic: duplicate name: SearchSomeServiceBody, new type: struct { Data string "json:\"data\"" }, existing type: struct { Search string "json:\"search\"" }

I'm pretty new to Go in general, but I wonder what's are the options to deal with this and maybe add "type" aka Input/Output to the generated name? I don't really want to add those suffixes to struct names.