You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've heard that go 1.11 is shipping with experimental support for modules. Currently counterfeiter does not support modules but it sounds like it could be interesting to try.
Personally I don't have many opportunities to write golang anymore, and the size and scope of this effort is a bit hard for me to imagine. If anyone interested in this could help me out by leaving a comment in this issue helping to describe use cases for counterfeiter with modules, I would be oh so grateful for your help.
For example:
AS an application developer
WHEN my application uses a custom module I built
AND I run the command `counterfeiter tim/does/not/know/what/args/to/put/here`
THEN I should see that something cool has happened.
Keeping your use cases as specific and narrowly constrained as possible, while highlighting edge cases or additional features you can imagine will really help ensure that we can build something useful to support modules (if someone ends up finding the time to develop this feature).
The text was updated successfully, but these errors were encountered:
I've heard that go 1.11 is shipping with experimental support for modules. Currently counterfeiter does not support modules but it sounds like it could be interesting to try.
Personally I don't have many opportunities to write golang anymore, and the size and scope of this effort is a bit hard for me to imagine. If anyone interested in this could help me out by leaving a comment in this issue helping to describe use cases for counterfeiter with modules, I would be oh so grateful for your help.
For example:
Keeping your use cases as specific and narrowly constrained as possible, while highlighting edge cases or additional features you can imagine will really help ensure that we can build something useful to support modules (if someone ends up finding the time to develop this feature).
The text was updated successfully, but these errors were encountered: