Remove output related to fixed issue (#1244) #2428#2429
Merged
dilipkrish merged 1 commit intospringfox:masterfrom May 31, 2018
Merged
Remove output related to fixed issue (#1244) #2428#2429dilipkrish merged 1 commit intospringfox:masterfrom
dilipkrish merged 1 commit intospringfox:masterfrom
Conversation
Codecov Report
@@ Coverage Diff @@
## master #2429 +/- ##
============================================
+ Coverage 95.41% 95.42% +<.01%
- Complexity 2956 2957 +1
============================================
Files 336 336
Lines 7856 7849 -7
Branches 620 620
============================================
- Hits 7496 7490 -6
Misses 227 227
+ Partials 133 132 -1 |
Member
|
Thanks for the PR @haelduksf !! |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I noticed some descriptions in my documentation like
@Size: Min - Max (until #1244 gets fixed). Looks like that was fixed back in 2.5, and I see the correct "minimum" and "maximum" values for all of them, so I opened #2428 and got rid of the generated message.