Jeff Hodges comments

Results 83 comments of


                                            Jeff Hodges

Gazelle deletes grpc dependencies if put mock in a go_library. Possible output mock file in directory instead of bazel-in?

Hm, I wonder if there's a way for bazel_gomock to convince gazelle to leave this alone without special casing. Generating a file to go into source hasn't, in the past,...

setting default package name when self_package is known

Could you post the build target you're needing to use this in? I'm trying to figure out how this and #28 are operating differently

setting default output file name

Hm, I'm worried about this one because there's no way for folks to know what to include in their other targets to use this one.

setting default output file name

Do you have any ideas on how to solve that?

setting default output file name

Right! If we can get a README update in this patch, that'd be cool!

Mock system packages

I have a workaround for you and have [opened a ticket](https://github.com/bazelbuild/rules_go/issues/1944) with the rules_go folks to make a nicer solution. It looks like there's no bazel targets for individual packages...

Mock system packages

(I'm pretty sure that you don't have to export that type alias, too, if the alias is in the same package as the generated and test code but haven't checked...

Mock system packages

(Typoed the `interfaces` param values in the original comment, but have corrected it)

Add a proc macro for exceptions

Saw this had a `Good First Issue` on it and I was wanting exception types with some fields attached, so I tried a quick swipe at this derive macro in...

Add a proc macro for exceptions

> You shouldn't have to do that - nothing in the macro crate has any idea about pyo3's types. > > Do you have experience writing proc macros? Ah, the...