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
Run mockolo -s <SOURCE> -d <DESTINATION> on the source folder which doesn't have protocols with mockable annotation.
It generated a file without any mocks.
What did you expect to happen?
I'd expect the empty file won't be created. Or at least having a flag which allows to skip creation of those empty files.
I recognise that the tools also will need to remove the destination file in that case which adds some complications but still, arguable it's worth it.
What is the use-case
If in a modularised project the script is executed once per module, modules which not yet added mock annotation will end up having empty files which is not ideal.
I want to ensure that first-time users are not confused if no file is generated.
If it's a matter of feelings, I'm curious to know if there are others who agree.
What did you do?
Run
mockolo -s <SOURCE> -d <DESTINATION>
on the source folder which doesn't have protocols withmockable
annotation.It generated a file without any mocks.
What did you expect to happen?
I'd expect the empty file won't be created. Or at least having a flag which allows to skip creation of those empty files.
I recognise that the tools also will need to remove the destination file in that case which adds some complications but still, arguable it's worth it.
What is the use-case
If in a modularised project the script is executed once per module, modules which not yet added mock annotation will end up having empty files which is not ideal.
Mockolo Environment
Mockolo Version: 2.0.1
Dependency Manager: Homebrew
Xcode Version: 15.0
The text was updated successfully, but these errors were encountered: