Suhas Karanth

The problem is around adding the import for a type alias - [googleapis/google-cloud-go@`pubsub`/v1.15.0/pubsub/message.go#L37](https://github.com/googleapis/google-cloud-go/blob/pubsub/v1.15.0/pubsub/message.go#L37). I have added a test case for the same in #155. For some reason, while [parsing the...

I had tried asking for help on Gophers slack as well but I was not able to use the suggestions to arrive at a solution for the problem of type...

Yes, I also agree that `moq` shouldn't prevent this. However, I am not sure if the changes required are quite as simple. If we set `Tests: true` while loading packages,...

A possible workaround is to use a private interface definition: ```go // dynamo.go package dynamo import "github.com/aws/aws-sdk-go-v2/service/dynamodb/dynamodbiface" //go:generate moq -out ../mocks/dynamodb.go -pkg mocks . dynamoDBAPI:DynamoDBAPI type dynamoDBAPI = dynamodbiface.DynamoDBAPI ```

Blocked by both the Travis CI zombie as well as https://github.com/actions/setup-go/issues/68.

Replaced by #135. Changes are essentially the same but wanted to shift focus from migrating to different CI to Go modules migration.

A bit hesitant to increase the API surface area, not sure if it would be useful for the majority. Perhaps it could be added as a method depending upon an...

While I agree that having to repeat the name _ideally_ should not have been necessary, it does not seem feasible to solve this without breaking backwards compatibility. And in this...

How does this compare to configuring it directly in the package.json? Saves having to configure repetitively for each new workspace, right? Adding a workspace folder _should_ be a rare activity...

Don't have any additional instructions that I could share. If you could share a minimal repo that can be used to reproduce the issue, I can try to take a...