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. @tdayris is currently working on unifying the handling of Java memory specifications in wrappers where the bioconda recipes allow for this. This leads to rather large blocks of code that is repeated across all the respective recipes and whenever we want to change the strategy of memory handling, we will have to edit all those places in sync. See here: #204 (comment)
Describe the solution you'd like
I would like to have some kind of common or utils module that provides useful functions. In the case above, it would e.g. need to take the snakemake object and a java_opts string variable as parameters and would adjust the java_opts string accordingly with the Java memory option.
Describe alternatives you've considered
The alternative is keeping all those copies of code around. This might make the wrappers more readable, as no reference to another code file is needed. But as described above, it incurs the maintenance burden of having to keep all those code blocks in sync.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
@tdayris is currently working on unifying the handling of Java memory specifications in wrappers where the bioconda recipes allow for this. This leads to rather large blocks of code that is repeated across all the respective recipes and whenever we want to change the strategy of memory handling, we will have to edit all those places in sync. See here:
#204 (comment)
Describe the solution you'd like
I would like to have some kind of
common
orutils
module that provides useful functions. In the case above, it would e.g. need to take the snakemake object and ajava_opts
string variable as parameters and would adjust the java_opts string accordingly with the Java memory option.Describe alternatives you've considered
The alternative is keeping all those copies of code around. This might make the wrappers more readable, as no reference to another code file is needed. But as described above, it incurs the maintenance burden of having to keep all those code blocks in sync.
The text was updated successfully, but these errors were encountered: