So far the logic for determining the filename used to write the content of the inputs nodes in the running directory to, was to first look if an explicit filename was defined in the filenames input and otherwise to fallback to the key of the node within the nodes dictionary.
Here we change the code to use the filename of the SinglefileData before falling back to the key, if and only if the filename of the node is defined and not SinglefileData.DEFAULT_FILENAME. This last exception is important because if a SinglefileData node is constructed without explicit filename, that value is used, and with this new fule any SinglefileData nodes that were created without explicit filename will end up overwriting each other.
Fixes #24
So far the logic for determining the filename used to write the content of the inputs
nodesin the running directory to, was to first look if an explicit filename was defined in thefilenamesinput and otherwise to fallback to thekeyof the node within thenodesdictionary.Here we change the code to use the
filenameof theSinglefileDatabefore falling back to the key, if and only if thefilenameof the node is defined and notSinglefileData.DEFAULT_FILENAME. This last exception is important because if aSinglefileDatanode is constructed without explicit filename, that value is used, and with this new fule anySinglefileDatanodes that were created without explicit filename will end up overwriting each other.