I saw that the relatively new filemerger node from me an Alex does only merge the first URI from every merged port.
That comes from the fact that we use the functionality of creating a FileStoreReferenceURIPortObject which seems to limit to only the first URI.
Question: Can this class be extended or should one find an alternative solution. I was struggling on how to allow both Abstractfilestoreportobjects from e.g. a ZiploopEnd as well as the usual URIPortObjects. In general, I still did not get the complete difference between them.
I guess this is a minor issue and don't know if we even should support it.
Okay, preparing a fix. The reason was that a FileStoreReferenceURIPortObject could not be used to create a new one and was I think only designed for a single file (to collect loop results).
I saw that the relatively new filemerger node from me an Alex does only merge the first URI from every merged port. That comes from the fact that we use the functionality of creating a FileStoreReferenceURIPortObject which seems to limit to only the first URI. Question: Can this class be extended or should one find an alternative solution. I was struggling on how to allow both Abstractfilestoreportobjects from e.g. a ZiploopEnd as well as the usual URIPortObjects. In general, I still did not get the complete difference between them. I guess this is a minor issue and don't know if we even should support it.