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
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 if mockery accepted this as a valid case and no-oped instead of failing.
Mockery Version
v2.43.2
Golang Version
1.22.4
Installation Method
Binary Distribution
Docker
brew
go install
Other: [specify]
Steps to Reproduce
Create a .mockery.yaml config with the contents:
with-expecter: true
Run mockery
Expected Behavior
Successful run with no generation.
Actual Behavior
Error
09 Jul 24 11:12 EDT FTL Use --name to specify the name of the interface or --all for all interfaces found dry-run=false version=v2.43.2
The text was updated successfully, but these errors were encountered:
austince
changed the title
Support
Support empty .mockery.yaml config
Jul 9, 2024
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
The text was updated successfully, but these errors were encountered: