This repository has been archived by the owner on Mar 23, 2023. It is now read-only.
fix: only remove extension from path when it is non-empty #47
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 default config for root datastores is to have an empty string extension, but if you use putRaw or getRaw as the sharded datastore does, stripping the extension can cause the final file path to be an empty string, so guard on the extention not having a valid length.
achingbrain
changed the title
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 default config for root datastores is to have an empty string extension, but if you use putRaw or getRaw as the sharded datastore does, stripping the extension can cause the final file path to be an empty string, so guard on the extension not having a valid length.