You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The current implementation requires duplicating the interface configuration for each output path where the file needs to be generated. This results in unnecessary repetition, increases maintenance efforts, and makes managing multiple output paths cumbersome.
Describe the solution you'd like
We propose adding support for specifying a list of output paths within a single interface configuration. This would allow the generation of output files in multiple locations from the same interface, reducing duplication and simplifying the configuration process
Describe alternatives you've considered
An alternative considered is to continue with the current approach of duplicating interfaces for each output path. However, this solution is inefficient and prone to errors, as any change to the interface would require updating all duplicate configurations.
Additional context
This enhancement would streamline the process of managing output files across different locations, making the interface configuration more maintainable and reducing the likelihood of configuration errors. It would also make the feature more flexible for use cases that require outputs in multiple directories.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
The current implementation requires duplicating the interface configuration for each output path where the file needs to be generated. This results in unnecessary repetition, increases maintenance efforts, and makes managing multiple output paths cumbersome.
Describe the solution you'd like
We propose adding support for specifying a list of output paths within a single interface configuration. This would allow the generation of output files in multiple locations from the same interface, reducing duplication and simplifying the configuration process
Describe alternatives you've considered
An alternative considered is to continue with the current approach of duplicating interfaces for each output path. However, this solution is inefficient and prone to errors, as any change to the interface would require updating all duplicate configurations.
Additional context
This enhancement would streamline the process of managing output files across different locations, making the interface configuration more maintainable and reducing the likelihood of configuration errors. It would also make the feature more flexible for use cases that require outputs in multiple directories.
The text was updated successfully, but these errors were encountered: