-
Notifications
You must be signed in to change notification settings - Fork 8k
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
upgrade validator version to v9 #1015
Conversation
build fail. missing some package. |
validator removes exists tag from v8 to v9, this update may break some users' apps |
Codecov Report
@@ Coverage Diff @@
## master #1015 +/- ##
=======================================
Coverage 98.69% 98.69%
=======================================
Files 40 40
Lines 2225 2225
=======================================
Hits 2196 2196
Misses 16 16
Partials 13 13
Continue to review full report at Codecov.
|
Please hold this PR, need to clarify if this (#1015) and #990 should be considered breaking and need a major version bump, or a warning in the changelog is ok for a minor version bump (v1.3 milestone) |
note: review #430 (comment) |
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.
Is the same example that validator provides, i add to my project and not break
Wondering what the status of this is - does somebody need to submit another PR? |
@aadidenko nobody, only the pr, waiting for review. |
Ok, yall, I think we need to prioritize this PR. My users need emojis in their usernames. |
Is there another way to upgrade to v9 without waiting for this PR to get merged in? |
Validator V9 includes |
oh here it is, mark this one too |
Any updates on this PR? Validator V9 would be really useful! |
Maybe we should upgrade milestone v1.4.0, ping @javierprovecho @appleboy thanks! |
@thinkerou @appleboy can we get this merged in? |
Any news? |
1 similar comment
Any news? |
@thinkerou |
@always-waiting sorry, the issue need @javierprovecho review and agree! thanks! |
@thinkerou what are you thinking in regards to moving forward with |
I also like KISS, about the pull request we should wait @javierprovecho review as your said #1015 (comment), upgrade to v9 isn't urgent, so we should wait his reply. |
@appleboy we should merge to gin1.5 branch now? thanks! |
@thinkerou Please fix the conflict. Could it release it as next versions after merging this branch? In my view, this issue is more important than other. We desire to use the latest validation to enhance current error message readability. To compare other issues in 1.5 milestone, those are bug fix and feature enhancements. It seems it’s not critical for current gin. Those can postpone to future version. To focus simple and important issue, let the PR get merged and the new change get released fast. In short, we hope the 1.5 or any milestone’s scope could get reduced or classify more and small task. It ensures the release can ship fast to developer. In personal, I am very expected every new release of gin, we will use the new feature to simplify our development. Thanks. If other gin fans have any idea, please comment here. I want to know what you expect and discuss here. Thanks. |
The PR still doesn't expose the validator object. |
Any progress on getting this released? |
@thinkerou Please fix the conflict. |
@appleboy done |
As #1015 (comment) said, we need to add breaking change log and merge it now, right? @appleboy |
@thinkerou Yes, we need to write some changes like features or bug fix in CHANGELOG.md for next release version. |
@appleboy OK, thanks! merged. |
* upgrade validator version to v9 * Update vendor.json * Update go.mod * Update go.sum * fix * fix * fix bug * Update binding_test.go * Update validate_test.go * Update go.sum * Update go.mod * Update go.sum * Update go.mod * Update go.sum
No description provided.