Closed carmelogallo closed 3 years ago
Now
includeResources
is used for the whole templates you've added. So then it'sfalse
then new generated files will be just empty. It has no sense. What if we can put that templates understencils/resources
and include this path inside*.yml
on demand:templates: - ./stencils/ - ./stencils/resources
Then it will include resource relates templates / generate files
@avdyushin File won't be empty since Sourcery won't add the file :)
Now
includeResources
is used for the whole templates you've added. So then it'sfalse
then new generated files will be just empty. It has no sense. What if we can put that templates understencils/resources
and include this path inside*.yml
on demand:templates: - ./stencils/ - ./stencils/resources
Then it will include resource relates templates / generate files
@avdyushin File won't be empty since Sourcery won't add the file :)
But it will be generated right? Eventually it can be configure to be added into Xcode project automatically (no need to drag'n'drop). So I'd prefer not to see empty files at all :)
But it will be generated right? Eventually it can be configure to be added into Xcode project automatically (no need to drag'n'drop). So I'd prefer not to see empty files at all :)
No. That's the point. Sourcery won't generate the file at all :)
But it will be generated right? Eventually it can be configure to be added into Xcode project automatically (no need to drag'n'drop). So I'd prefer not to see empty files at all :)
No. That's the point. Sourcery won't generate the file at all :)
Ah, nice, fine by me then
Now
includeResources
is used for the whole templates you've added. So then it'sfalse
then new generated files will be just empty. It has no sense. What if we can put that templates understencils/resources
and include this path inside*.yml
on demand:Then it will include resource relates templates / generate files