-
Notifications
You must be signed in to change notification settings - Fork 9
SIMSBIOHUB-544: Update project/survey start/end date constraints #1245
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
Conversation
…vey dates being between project dates. Update associated yup schema.
|
Openshift URLs for the PR Deployment: |
al-rosenthal
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.
the new trigger works but I noticed that the survey end date component is still warning that End Date cannot come after the Project End Date
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## dev #1245 +/- ##
==========================================
+ Coverage 54.56% 54.57% +0.01%
==========================================
Files 599 599
Lines 18392 18387 -5
Branches 2837 2832 -5
==========================================
Hits 10035 10035
+ Misses 7703 7698 -5
Partials 654 654 ☔ View full report in Codecov by Sentry. |
mauberti-bc
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.
Created Projects and Surveys with non-overlapping dates 👍
curtisupshall
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.
Code looks good to me
|
Please retry analysis of this Pull-Request directly on SonarCloud |
Update associated yup schema.
Links to Jira Tickets
https://apps.nrs.gov.bc.ca/int/jira/browse/SIMSBIOHUB-544
Description of Changes
Update project and survey date triggers to remove restrictions on survey dates being between project dates.
Update associated yup schema.
Why? The triggers were not complete (there were cases they didn't handle correctly) + the project dates are going to be deprecated in future. So this resolves the trigger issue (by removing the constraints altogether), and moves a few steps closer to the eventual goal of removing the project dates.
Testing Notes
Project start date must always come before its own end date, as before.
Survey start date must always come before its own end date, as before, but now has no constraints related to the project dates. So a survey could start before a project, or start after the project has ended, etc.