feat: Add output_path
property, and streamline implementation
#50
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
About
Users got confused about the semantics of the
output_path_prefix
property. This patch makes it better by renaming it tooutput_path
, while still providing backwards-compatibility.Further, the
destination_path
property can also be used, thus this target can be a drop-in replacement to thehotgluexyz
variant.The value of the variable does not need to be configured using a trailing slash any longer. Instead, the implementation more thoroughly leverages
pathlib.Path
for concatenatingoutput_path
andfilename
.References
Thoughts
I am not sure about fc54324. I added it because mypy tripped like described in the commit message. Please educate me if that was wrong, so I will either remove it or amend it correspondingly.