-
Notifications
You must be signed in to change notification settings - Fork 15
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
6144 add check for exceeding max orders #6211
Open
fergie-nz
wants to merge
9
commits into
develop
Choose a base branch
from
6144-add-check-for-exceeding-max-orders
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains 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
And change to onSettled
github-actions
bot
added
bug
Something is borken
Team Ruru π¦
Roxy, Ferg, Noel
Severity: Hotfix
Extreme user impact. Can't finalise invoices. Needs patch release and installation immediately.
labels
Jan 21, 2025
Bundle size differenceComparing this PR to
|
roxy-dao
requested changes
Jan 21, 2025
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.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Something is borken
Severity: Hotfix
Extreme user impact. Can't finalise invoices. Needs patch release and installation immediately.
Team Ruru π¦
Roxy, Ferg, Noel
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.
Fixes #6144
π©π»βπ» What does this PR do?
Adds back end check to ensure we don't create program requisitions when the maximum number for that period has been reached.
Also adds front end error handling when attempting to create more than the specified number of
π Any notes for the reviewer?
I think we should spend time adding back end tests to creating program requisitions. Right now there is quite complicated logic with no tests validating.
Any fixes such as this one are time consuming to deal with. It is also currently unclear if there are other gaps in the logic without tests.
π§ͺ Testing
The way to test this using in app behaviour is to attempt to create duplicate requisitions which combined would exceed the maximum number together.
This requires 2 browsers:
π Documentation