[LIMS-1535] Lock out editing pre-session information 24h before session#7
Merged
[LIMS-1535] Lock out editing pre-session information 24h before session#7
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #7 +/- ##
==========================================
+ Coverage 93.77% 94.20% +0.42%
==========================================
Files 38 38
Lines 1527 1552 +25
==========================================
+ Hits 1432 1462 +30
+ Misses 95 90 -5 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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
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.
JIRA ticket: LIMS-1535
Summary:
Since modifying experimental parameters shortly before the session may confuse local contacts, it would be preferable to lock these out for regular users, and force them to email staff to make any further amendments.
Changes:
To test:
Either log in as a non-staff user, or comment line 90 in src/scaup/utils/session.py. Either way, these are tested in unit tests.
/shipments/2/preSession, check if 400 is returned/shipments/2/preSession, check ifisLockedis true