relative_to port on File module #1057
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Closed
remram44
force-pushed
the
relative-file-module
branch
5 times, most recently
from
8b30162
to
3f19916
Compare
This keeps the old behavior for the old workflows.
remram44
force-pushed
the
relative-file-module
branch
from
3f19916
to
dac5c3f
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Right now, if the 'name' set on a File module is relative, it will be relative to VisTrails's current working directory (the one it's started from).
This gives the choice between the location of the workflow, VisTrails's installation directory, and the working directory.
The only problem with this is module signatures: if you save your workflow somewhere else, you shouldn't hit the same cache entry.