🐛 Fix #importer_unzip_path logic
#1014
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
We discovered a bug with the previous updates to the `#importer_unzip_path` method where when the method is being called to create a path, it returns `nil` because the path does not exist and the whole reason why we are calling the method is to create the path. We add a `mkdir` argument to differentiate between when we're looking up the path vs wanting to create it.
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.
We discovered a bug with the previous updates to
the
#importer_unzip_pathmethod where when the method is being called to create a path, it returnsnilbecause the path does not exist and the whole reason why we are calling the method is to create the path.We add a
mkdirargument to differentiate between when we're looking up the path vs wanting to create it.