I'm aware of the hard-coded path and thought about it... Without packaging it as a module, it is hard to retrieve the root directory. At the moment I don't know a good solution, but you can open another issue of low priority for this.
I'm not really sure about the output/{project_name}/ path though- where is it mentioned? I thought all output would be written to sbat/output/.
Another thought:
Wouldn't it make sense to write the log at the location where the script is run? Let's assume someone creates an own project with individual input date and runs the module. It would be a bit counter-intuitive the log get's saved to the module directory. This only makes sense as long as you use the module by cloning the repo directly from github, but not if you install it. But we can move that discussion to later when we talk about packaging...
I'm aware of the hard-coded path and thought about it... Without packaging it as a module, it is hard to retrieve the root directory. At the moment I don't know a good solution, but you can open another issue of low priority for this. I'm not really sure about the
output/{project_name}/path though- where is it mentioned? I thought all output would be written tosbat/output/.Another thought: Wouldn't it make sense to write the log at the location where the script is run? Let's assume someone creates an own project with individual input date and runs the module. It would be a bit counter-intuitive the log get's saved to the module directory. This only makes sense as long as you use the module by cloning the repo directly from github, but not if you install it. But we can move that discussion to later when we talk about packaging...
Originally posted by @MarcoHannemann in https://github.com/ErikNixdorf/sbat/issues/46#issuecomment-1532926107