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
I currently do not allow this because mockery attempts to automatically determine if the output mock file is in the same package as the originating interface. I initially attempted to allow multiple packages in the output mock but was running into issues with this "is inpackage" determination, so I decided to defer this until later.
This is not theoretically impossible, it just requires extracting this logic out of the template generator constructor and into the logic that populates imports for each method.
The text was updated successfully, but these errors were encountered:
I currently do not allow this because mockery attempts to automatically determine if the output mock file is in the same package as the originating interface. I initially attempted to allow multiple packages in the output mock but was running into issues with this "is inpackage" determination, so I decided to defer this until later.
This is not theoretically impossible, it just requires extracting this logic out of the template generator constructor and into the logic that populates imports for each method.
The text was updated successfully, but these errors were encountered: