Open austince opened 2 months ago
If the intention is to use packages
, then there is no feasible way to do this until we move to v3 and remove legacy configuration semantics. The existence of the packages
config value is a feature flag that enables it. When mockery doesn't see this, it reverts to the old semantics.
Description
Support empty
.mockery.yaml
files. We have set up support for mockery for all packages in our repo but some do not (yet) need mocks. In order to avoid special-casing these packages in the generation commands, it would be great ifmockery
accepted this as a valid case and no-oped instead of failing.Mockery Version
v2.43.2
Golang Version
1.22.4
Installation Method
Steps to Reproduce
.mockery.yaml
config with the contents:Expected Behavior
Successful run with no generation.
Actual Behavior
Error