AP-5273: SCA level of service fix #7120
Merged
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.
What
Link to story
Update the SubstantiveDefaultsForm handling of the default level of service
On a non-sca proceeding the view stores default values and passes them as controller params to the form.
The SCA skip removed the submission of these and meant that the default LOS was not set
This updates the test to ensure the proceeding is instantiated in the same way that it occurs in the controller, i.e. no default values populated for the three substantive default level of service fields. It then updates the form to set the value using the values called from LFA and stored as form values
Checklist
Before you ask people to review this PR:
bundle exec rake
git rebase main
.