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
Currently we have to pass the whole path of the files as values to the flags -source and -destination.
eg: mockgen -source=D:\go_project\library_management\src\core\ports\repository.go -destination=D:\go_project\library_management\src\core\mocks\respository_mock.go
(In windows)
To reduce this redundancy in type, we can use the relative path.
Assuming mockgen is used from the targeted codebase.
The text was updated successfully, but these errors were encountered:
Hey @Abhishekkarunakaran, I see examples of relative paths being passed to the --source and --destination options for the mockgen command in the //go:generate comments of multiple files in the repository.
Currently we have to pass the whole path of the files as values to the flags -source and -destination.
eg:
mockgen -source=D:\go_project\library_management\src\core\ports\repository.go -destination=D:\go_project\library_management\src\core\mocks\respository_mock.go
(In windows)
To reduce this redundancy in type, we can use the relative path.
Assuming mockgen is used from the targeted codebase.
The text was updated successfully, but these errors were encountered: