fix: nonetype error when creating new folder #57
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
The new command uses the active view file name as the path from which to construct the new folder, but when the view is empty there is no real file on disk and the file name is None. The `os.path` functions like `isdir` and `exists` raise a NoneType exception when given None. This patch adds a NoneType check. Close braver#55 Re braver#56
|
Thanks! |
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.
The new command uses the active view file name as the path from which to construct the new folder, but when the view is empty there is no real file on disk and the file name is None.
The
os.pathfunctions likeisdirandexistsraise a NoneType exception when given None. This patch adds a NoneType check.Close #55
Re #56