if my package imports another package of the same name, the fake imports both about counterfeiter

[cryptix]

👍 also stumbled over this.

[ljfranklin]

We also ran into this. Any ideas on how we might fix this? We could change the package or the imports, but we'd rather not do either, as the package we're counterfeiting is purposely named the same as the package it imports as we are shadowing. e.g.

package sql

import (
    "database/sql"
)

type DB interface {
    Exec(query string, args ...interface{}) (sql.Result, error)
    Query(query string, args ...interface{}) (Rows, error)
}

[devoid]

Running into this issue as well. A simple solution would be to allow counterfeiter to generate a source file within the same package as the counterfeited interface. Is there any particular reason that the "${pkgname}/fakes" package was chosen?

[tjarratt]

@devoid mypackagename/fakes was chosen because it's separate from your implementation and it's fairly clear what is inside there. It's a good idea to keep your test doubles and test helpers separate from your actual code. Check out net/http and net/http/httptest in the standard library for some inspiration there.

That said, I think that this should be fixed. Any takers? Would love to help anyone that wants to work on a PR for this.

[joefitzgerald]

Is this still an issue in v6.0.0?