-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nesting include settings in .shed.yml (source as list)? #180
Comments
It seems to make sense to me - I like it. I don't think it is too complicated. An alternative implementation that might work to preserve the work in #158 is to preprocess the include_info entries such that each entry with a source list gets cloned n times with a single item and stuck back into the configuration. So modifying the code that calls |
The preprocessing idea should work - are there any benefits to doing the wildcard glob expansion earlier as well? |
Not that I can think of - and that would probably require reworking the logic for detecting if there are no matches. If it turns out to be cleaner to that earlier to though - that is fine. |
This allows nesting within the include setting of .shed.yml for example if you have a batch of files with the same strip_components setting. See GitHub issue galaxyproject#180.
Apologies - I didn't check my own work carefully enough yesterday. This example works: peterjc/pico_galaxy@226ce53
Giving:
However this fails: peterjc/pico_galaxy@1029aa9
The files under |
I think the problem (which manifests as a destination of |
Progress: Have to avoid |
Work in progress here: https://github.com/peterjc/planemo/tree/rel_paths |
Fixed with the merging of #196, closing issue. |
Consider a moderately complex
include
setting like this which is quite repetitive:It seems that currently
include
is a flat list of elements (defaulting tosource
entries if not a mini-dict), but allowing eachsource
entry to be a list would allow this kind of bundling:e.g. Something like this hack:
More work would be needed to preserve the work in #158 for spotting missing includes.
Also, harking back to #160 this would be possible too (but requires a few more tweaks to
planemo/shed/__init__.py
inrealize_to
to deal with implicit destinations of.
being used internally):Having played with this a bit, it would be an alternative solution to my proposal in #160, and might have some other future usecases - but overall I think it is too complicated?
The text was updated successfully, but these errors were encountered: