Rename forms api module to simple forms api #13035
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.
The Lighthouse team has an API named Forms API so they asked us to rename ours. Since our vets-website folder is called
simple-forms
we've chosen to rename fromforms_api
tosimple_forms_api
For reference: Original PR adding forms_api module
Summary
lib/simple_forms_api_submission
because this would require changes in devops, manifests, and AWS. We are not anticipating an issue with this for now. The main concern was stack traces that saidforms_api
Related issue(s)
Testing done
Used postman to test multiple requests locally and they worked as expected
Since there is no logic change the expected functionality is that vets-api starts up as expected without issues
Updated frontend forms that submit to this endpoint and tested locally that they submit correctly
Screenshots
Forms 26-4555, 21-4142, and 21-10210 submitting locally without issues to the new endpoint
What areas of the site does it impact?
A variety of forms that are non-prod
Associated PR to update those submission endpoints
Acceptance criteria