Issue 20: be more careful with file paths. #25
Merged
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
Check if provided .sup file name includes '/' or '\'. If so, extract basename. Be more careful when creating file names and file paths inside `create_output_fn_dir()`.
|
Looks good. I hope it still works in all cases it worked before? |
|
If you're asking if I have run any sort of systematic tests, I have not. I ran it with |
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.
Check if provided .sup file name includes '/' or ''. If so, extract basename. Be more careful when creating file names and file paths inside
create_output_fn_dir().A more comprehensive rework of
create_output_fn_dir()maybe later.