-
Notifications
You must be signed in to change notification settings - Fork 1.9k
fix: updates validate_date check for publishing draft event #6246
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
fix: updates validate_date check for publishing draft event #6246
Conversation
Codecov Report
@@ Coverage Diff @@
## development #6246 +/- ##
===============================================
- Coverage 65.6% 65.57% -0.04%
===============================================
Files 286 286
Lines 14559 14567 +8
===============================================
Hits 9552 9552
- Misses 5007 5015 +8
Continue to review full report at Codecov.
|
kushthedude
left a 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.
LGTM
|
@iamareebjamal @uds5501 @mrsaicharan1 please review |
de451ee to
7f29066
Compare
|
Verify other changes in PATCH don't affect this |
|
@iamareebjamal I think we need the previous code block I added to update_object -
Currently, whole event data is passed even if a field is updated or not. So, the date will always be checked if we don't specifically enters when it is to be tested. |
|
OK, split into 3 separate booleans with comments so that it is understandanble |
7f29066 to
00367e0
Compare
00367e0 to
380cb99
Compare
|
@iamareebjamal added comments for better understanding |
380cb99 to
0f7f1d2
Compare
8d3f8bd to
36bc417
Compare
fixes hound issues Adds boolean vars
36bc417 to
0ba351e
Compare
Fixes #6244
Short description of what this resolves:
User can publish past events.
Changes proposed in this pull request:
Checklist
developmentbranch.