-
Notifications
You must be signed in to change notification settings - Fork 1k
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
[WIP] Biotools #1891
base: dev
Are you sure you want to change the base?
[WIP] Biotools #1891
Conversation
To add a little bit of information here. |
:rtype: string | ||
""" | ||
try: | ||
return "/".join(tool_id.replace('repos', 'view', 1).split('/')[0:-2]) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Galaxy versions > 16.01 return a tool_shed_repository entry for toolshed tools that looks like this:
"tool_shed_repository": {"owner": "devteam", "changeset_revision": "e359ce20fbd9", "name": "fastq_quality_boxplot", "tool_shed": "toolshed.g2.bx.psu.edu"}
This is probably better suited for constructing a link, given that a toolshed may well be reachable at <http://server_url/abc/toolshed>
Sure, this does look really interesting. One thing that I would discuss is the use of tool_id ... it's a bit unfortunate that the same tool_id may not be sufficient to unambiguously identify the origin of a tool. AFAIK we'd need a combo of toolshed/owner/name/changeset_revision. |
lib/galaxy/datatypes/data.py
Outdated
edam_format = "format_1915" | ||
edam_data = "data_0006" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
edam_data
is duplicated here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@nsoranzo feel free to PR against this branch. I can merge it afaik.
'datatypes', | ||
path_prefix='/api', | ||
collection={ 'sniffers': 'GET', 'mapping': 'GET', 'converters': 'GET', 'edam_data': 'GET' }, | ||
parent_resources=dict( member_name='datatype', collection_name='datatypes' ) ) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that instead of invoking again webapp.mapper.resource()
here, you should just add 'edam_data': 'GET'
at line 303.
else: | ||
return description[0].upper() + description[1:size] + '.' | ||
except IndexError: | ||
raise description |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will cause a TypeError if description is ""
.
'dataDescription': data_json['name'] | ||
}) | ||
|
||
def inputs_extract_repeat(repeat_json): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there not already a function in Galaxy that traverses all params and extracting data
-params.
If not this should probably end up in some utils file to be reused by other modules.
This has been rebased now that #2387 is merged. |
@galaxybot test this |
@hmenager What's the status of this? Shall we hack on it next week? |
No description provided.