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.
What this PR does / why we need it:
This PR has following fixes #1002, #1003 , #1010, #1057, #1061, #1062, #1063, #1064
Which issue this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close that issue when PR gets merged): fixes #Special notes for your reviewer:
Test Report for issues is as follows:
#1002 Non utf-8 characters file name is creating db entry
#1003 Special characters in file share name is not supported by backend
#1010 Updating the fileshare description and name when file share status is error
#1057 Duplicate file share name causing the existing share status as error
#1061 Updating file share name with empty string should not be allowed
It takes the request but doesn't update, swagger validation is not throwing for minimum name length of fileshare but actual validation is blocking to create empty name string file share
#1062 Updating file share name with special characters
#1063 Updating file share name length should be grater than 102 characters
#1064 Updating file share description with non utf-8 code characters
Release note: