civiform
civiform copied to clipboard
Store the endpoint used for the selected address correction option
Description
Please explain the changes you made here.
Release notes
The title of the pull request will be used as the default release notes description. If more detail is needed to communicate to partners the scope of the PR's changes, use this release notes section.
Checklist
General
Read the full guidelines for PRs here
- [ ] Added the correct label: < feature | enhancement | bug | under-development | dependencies | infrastructure | ignore-for-release | database >
- [ ] Assigned to a specific person,
civiform/developers
, or a more specific round-robin list - [ ] Added an additional reviewer from outside your organization as FYI (if the primary reviewer is in the same organization as you)
- [ ] Created unit and/or browser tests which fail without the change (if possible)
- [ ] Performed manual testing (Chrome and Firefox if it includes front-end changes)
- [ ] Extended the README / documentation, if necessary
Database evolutions
Read the guidelines here
- [ ] Assigned two reviewers
- [ ] Guarded against already existing resources using
IF NOT EXISTS
andIF EXISTS
- [ ] Downs created to undo changes in Ups
User visible changes
- [ ] Followed steps to internationalize new strings
- [ ] Added context strings to new messages
- [ ] Didn't use a message in applicant facing code that isn't translated yet (unless behind a flag)
- [ ] Wrote browser tests using the validateAccessibility method
- [ ] Tested on mobile view. See mobile device mode
- [ ] Manually tested at 200% size
- [ ] Manually evaluated tab order
New Features
- [ ] Add new FeatureFlag env vars to
server/conf/helper/feature-flags.conf
- [ ] Conditioned new functionality on a FeatureFlag
- [ ] Wrote browser tests with the feature flag off and on, etc.
Instructions for manual testing
If instructions are needed for manual testing by reviewers, include them here.
Issue(s) this completes
Fixes #<issue_number>; Fixes #<issue_number>...