-
Notifications
You must be signed in to change notification settings - Fork 316
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
File share name fixes #1084
Open
Shruthi-1MN
wants to merge
1
commit into
sodafoundation:development
Choose a base branch
from
Shruthi-1MN:fileshare_name_fixes
base: development
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
File share name fixes #1084
Shruthi-1MN
wants to merge
1
commit into
sodafoundation:development
from
Shruthi-1MN:fileshare_name_fixes
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
Shruthi-1MN
force-pushed
the
fileshare_name_fixes
branch
3 times, most recently
from
November 22, 2019 10:55
c4e14c9
to
14144ee
Compare
Codecov Report
@@ Coverage Diff @@
## development #1084 +/- ##
==============================================
- Coverage 34.92% 34.82% -0.1%
==============================================
Files 97 97
Lines 17563 17627 +64
==============================================
+ Hits 6133 6139 +6
- Misses 10561 10615 +54
- Partials 869 873 +4
|
Shruthi-1MN
force-pushed
the
fileshare_name_fixes
branch
4 times, most recently
from
November 25, 2019 06:27
0393f81
to
c5a3c2a
Compare
joseph-v
reviewed
Nov 25, 2019
wisererik
reviewed
Nov 26, 2019
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it's better add constraint into swagger api. The api filter will help you do the validation.
Shruthi-1MN
force-pushed
the
fileshare_name_fixes
branch
4 times, most recently
from
December 11, 2019 09:46
1e90bd1
to
d24a534
Compare
Shruthi-1MN
force-pushed
the
fileshare_name_fixes
branch
7 times, most recently
from
January 3, 2020 11:06
9585c88
to
d5091b2
Compare
Shruthi-1MN
force-pushed
the
fileshare_name_fixes
branch
from
January 3, 2020 11:16
d5091b2
to
6055098
Compare
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.
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: