When the bound of a generic is declared in the same package as the output package of the generated mocks, the output would attempt to import the current package, causing an import loop error in gopls (don't remember the error by go test).
This fixes it by using the existing sanitizing routines but by passing the correct data down.
When the bound of a generic is declared in the same package as the output package of the generated mocks, the output would attempt to import the current package, causing an import loop error in gopls (don't remember the error by go test).
This fixes it by using the existing sanitizing routines but by passing the correct data down.