Two-part tariff review pages - Removing validation #1084
Merged
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
https://eaflood.atlassian.net/browse/WATER-4497 During the testing for the two-part tariff review pages, it was found that some of the validation on the amend pages where too restrictive. The volumes or adjustments entered both had minimum and maximum values set. The billing and data team after testing the engine found these to be too restrictive and they needed the ability to go higher then the max amount. This PR is removing the validation for the range that a user can enter.
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.
https://eaflood.atlassian.net/browse/WATER-4497
During the testing for the two-part tariff review pages, it was found that some of the validation on the amend pages where too restrictive. The volumes or adjustments entered both had minimum and maximum values set. The billing and data team after testing the engine found these to be too restrictive and they needed the ability to go higher than the max amount. This PR removes the validation for the range that a user can enter.