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
Scottx611x/expose extra directories #2447
Conversation
refinery/tool_manager/models.py
Outdated
self.NODE_INFORMATION: self._get_detailed_input_nodes_dict(), | ||
ToolDefinition.EXTRA_DIRECTORIES: ( | ||
self.tool_definition.get_extra_directories() | ||
) |
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 don't think you need the surrounding paren here: There's no syntactic ambiguity without it.
refinery/tool_manager/models.py
Outdated
self.NODE_INFORMATION: self._get_detailed_input_nodes_dict(), | ||
ToolDefinition.EXTRA_DIRECTORIES: ( | ||
self.tool_definition.get_extra_directories() | ||
) |
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 don't think this should block, but the mix of self
and ToolDefinition
, or public and underscored confuses me, a little. Are those distinctions useful, and meaningful?
… make less wordy since Parameters at the moment require all of these fields.
…com/refinery-platform/refinery-platform into scottx611x/expose_extra_directories
Failing build See: #2348 |
@mccalluc Please review/merge #2446 Before this one
extra_directories
information toinput.json
Note:
Heatmap Scatterplot
Tool launches properly with these changes, but we run into the relative paths issue again (when specifying a relative path in a VisTool things get routed through Refinery instead of the proxy) . We should really begin looking into using subdomain based routing for Vis Tools