General Design Thoughts
i would rename "FileService" to something more explicit
do you need any kind of modularity/expandability? if so then you can think of isolating logic in services more, if not you could kinda do everything in FileService for me, as long as logic is well understandable still
for example supposing this is a self contained program you could keep the FileService as a lower layer and have a series of classes that deal with the different types of output that get injected into it
or it could even be a parameter of a method
the situation is a bit unclear, like are you accessing more than one file? are these data unrelated? are you writing multiple files or multiple sheets into one file?
do you need any kind of modularity/expandability? if so then you can think of isolating logic in services more, if not you could kinda do everything in FileService for me, as long as logic is well understandable still
for example supposing this is a self contained program you could keep the FileService as a lower layer and have a series of classes that deal with the different types of output that get injected into it
or it could even be a parameter of a method
the situation is a bit unclear, like are you accessing more than one file? are these data unrelated? are you writing multiple files or multiple sheets into one file?
