Nothing currently prevents rate adjustments from summing > 1, which is impossible for the model!
This should be handled on the form request itself when the user is updating rates, so we can feed back to users that the request they are making cannot be allowed. So when a user enters an adjustment in the form we should calculate the new rates and return an error message to the user if it sums > 1
We need to think about this only for transition rates (not entry rates), so there are two forms that are relevant:
[ ] views.exit_rates(): somewhere in the acceptance of the new rates (lines 725-734)
[ ] views.transition_rates(): again, somewhere in the acceptance (lines 842-848)
Nothing currently prevents rate adjustments from summing > 1, which is impossible for the model!
This should be handled on the form request itself when the user is updating rates, so we can feed back to users that the request they are making cannot be allowed. So when a user enters an adjustment in the form we should calculate the new rates and return an error message to the user if it sums > 1
We need to think about this only for transition rates (not entry rates), so there are two forms that are relevant:
Realistically, this is dependent on: