[storage]Fixed an issue of escaping slashes in blob name unnecessarily. #23461
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
EmmaZhu
requested review from
XiaoningLiu,
jeremymeng,
vinjiang,
jiacfan and
ljian3377
as code owners
ghost
added
the
|
API change check API changes are not detected in this pull request. |
jiacfan
approved these changes
Oct 13, 2022
jiacfan
reviewed
Oct 13, 2022
| /** | ||
| * Escape the file or directory name but keep path separator ('/'). | ||
| */ | ||
| export function EscapePath(pathName: string): string { |
There was a problem hiding this comment.
May consider to add test for path with or without /.
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.
Packages impacted by this PR
@azure/storage-blob
@azure/storage-file-datalake
@azure/storage-file-share
Issues associated with this PR
Describe the problem that is addressed by this PR
What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
Are there test cases added in this PR? (If not, why?)
Provide a list of related PRs (if any)
Command used to generate this PR:**(Applicable only to SDK release request PRs)
Checklists