Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add build tag support #145

Merged
merged 3 commits into from
May 20, 2017
Merged

Add build tag support #145

merged 3 commits into from
May 20, 2017

Conversation

codeactual
Copy link
Contributor

Should resolve #109 by reusing go/build.Context.MatchFile to know if we should include a given file.

(tests results on Windows)

Copy link
Contributor

@tamccall tamccall left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ran all tests on my Ubuntu box everything looks good to me
build-results.txt

@@ -0,0 +1,24 @@
package mockery
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was thinking about doing this the other day 👍

@jmalloc
Copy link

jmalloc commented Apr 28, 2017

Any chance this could be merged? I'd love to make use of this :)

@evanphx evanphx merged commit 0b3b3df into vektra:master May 20, 2017
LandonTClipp pushed a commit to LandonTClipp/mockery that referenced this pull request Oct 19, 2023
When the type and the package name is the same for an anonymous
parameter (ex: time.Time), and there are more than 1 such parameters,
the generated name for both was the same. And the generated code would
not be valid.

Fix the bug by ensuring the parameter name does not conflict with
package imports first before checking against other parameter names.
LandonTClipp pushed a commit to LandonTClipp/mockery that referenced this pull request Nov 20, 2023
When the type and the package name is the same for an anonymous
parameter (ex: time.Time), and there are more than 1 such parameters,
the generated name for both was the same. And the generated code would
not be valid.

Fix the bug by ensuring the parameter name does not conflict with
package imports first before checking against other parameter names.
LandonTClipp pushed a commit to LandonTClipp/mockery that referenced this pull request Dec 23, 2023
When the type and the package name is the same for an anonymous
parameter (ex: time.Time), and there are more than 1 such parameters,
the generated name for both was the same. And the generated code would
not be valid.

Fix the bug by ensuring the parameter name does not conflict with
package imports first before checking against other parameter names.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Mockery appears to not respect build tags
4 participants