Need help to resolve cyclic dependency problem

I am working on one project at my company where I need to add a new interface and it's implementation to the existing code. While I did that, I came across a challenging situation where I am hit with cyclic dependency issue.

Here are further details:
Project directory: test-cyclic-dependency
Existing code is in File1: test-cyclic-dependency/model/state/model.go

package state

import ("test-cyclic-dependency/model")

type CollectionByCollectionName struct {
	CollectionName string
	imOfTypeInModel model.STRING
}

I need to define a new interface Search in File2: test-cyclic-dependency/model/search.go

package model

import (
	"test-cyclic-dependency/model/state"
)

type Search interface {
	Search(keyword string) state.CollectionByCollectionName
}

type STRING string

This code resulting into cyclic dependency error as below:

# go build model/state/model.go 
package command-line-arguments
	imports test-cyclic-dependency/model
	imports test-cyclic-dependency/model/state
	imports test-cyclic-dependency/model: import cycle not allowed

Could someone help me to address this issue? Would there be a way to resolve it keeping the code organisation the same?

To break the dependency cycle move type STRING string into the state package (as that's only place where it is used - so I guess it is related to it) and remove model import from state package. Alternatively, if it does not fit there logically move type STRING string into its own third package and only import that in the state package.

NOTE: I assume type STRING is just placeholder for something more meaningful to keep your example simple. There's no point in having type STRING string at all. If you remove it and just use string you no longer need to import model in state.

Resolved it by moving the Search interface to a new separate package 'search'.

Thank you all for helping me in this.

Thanks and Regards,
Prafulla.