hel
hel copied to clipboard
nelsam
Hel rules over Helheim, where the souls unworthy of Valhalla reside. It's also a mock generator for Go.
We usually don't want to generate mocks for interface types in other packages, to help reduce the urge to use massive interface types as the source of truth for what...
When mocking a type which has other interface types as dependencies, the package name used as a selector is the local alias. This causes issues with the later call to...
Our local package name logic is working in _most_ cases, but I've just encountered a case where `chan (chan
It'd be nice to 'opt-out' of generating some interfaces with something like ``` hel: no ``` Heh, or whatever
It seems like `prependLocalPackage` is not always being called on dependencies.
We need to support relative imports for things like flattening imports and resolving dependent types.
This is a pretty important note - hel has thus far been assuming that tests can only be in the test package _or_ the non-test package, not both. Turns out...
Say we have an integration test package that requires a mock from an interface. Hel does not analyze the test code at all. I think I would would want to...
Instead of methods blocking by default, changed blocking return behavior to require user activation. Also created an additional channel that can be used to unblock a mock method call once...
Mock actually ends up being invalid. Interface: ``` go package foo import baz "bar" type Buz interface { Close() (baz.Thing) } ``` Generated a mock with `baz` prefixes but no...
