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
Can we use by default deeptools_bamCompare:?
If people want to specify versions and be very strict they could use toolshed.g2.bx.psu.edu/repos/bgruening/deeptools/deeptools_bamCompare/3.2.1+galaxy1:
Thoughts?
The text was updated successfully, but these errors were encountered:
The tool id is currently matched as a regex, hence the wildcard. The idea was to provide a lot of flexibility in matching an arbitrary tool. In addition, I have some vague recollection of some other complication, but looking at the code now, I'm not sure what it might be and what you propose sounds doable. Also, agree that it would make the base case less complicated, so it's probably worthwhile taking another shot at this.
(not sure if this should be better discussed at the https://github.com/galaxyproject/tpv-shared-database repo)
Is there any reason we use the long-form IDs by default and need to add the
*
bits?I think https://github.com/galaxyproject/tpv-shared-database/blob/main/tools.yml#L35 makes it rather hard for contributors to add new tools if they only know the short ID. In addition, the long ID increases the chance of hard-to-spot errors.
Is there any reason we use the long IDs by default? And why do we need to add the
*
, can this not be done by TPV?In the example:
toolshed.g2.bx.psu.edu/repos/bgruening/deeptools/deeptools_bamCompare/.*:
Can we use by default
deeptools_bamCompare:
?If people want to specify versions and be very strict they could use
toolshed.g2.bx.psu.edu/repos/bgruening/deeptools/deeptools_bamCompare/3.2.1+galaxy1:
Thoughts?
The text was updated successfully, but these errors were encountered: