Change Details

NOTE: this involves **database changes** so all forms can support this change (address change (uses prefill), new donation, new membership ) **Acceptance Criteria** - The donation related code can accept and process street name and house number. **Implementation notes** - create 2 new database columns for street name and house number (don't delete the "legacy" street column) - that means: - write a new migration for adding the new columns - in fundraising-donations: - `AddDonationController` (->every controller we have that takes in data for a new address donation) needs to be able to retrieve the fields `streetName` and `houseNumber` and put it into the request. - `DonationConfirmationPresenter` needs to output the two new fields. - `Api\UpdateDonorController` needs to pass the two new fields to the `UpdateDonorRequest`. - `WMDE\Fundraising\Frontend\Presentation\DonationMembershipApplicationAdapter` needs to take the two new fields into account for prepopulating the membership application form. - Unit tests should check for the additional fields.

NOTE: this ticket https://phabricator.wikimedia.org/T369158 should be done first This ticket is about chaning the `fundraising-application` and use the new changes from the bounded contexts. **Acceptance Criteria** - The donation related code can accept and process street name and house number. **Implementation notes** - `AddDonationController` (->every controller we have that takes in data for a new address donation) needs to be able to retrieve the fields `streetName` and `houseNumber` and put it into the request. - `DonationConfirmationPresenter` needs to output the two new fields. - `Api\UpdateDonorController` needs to pass the two new fields to the `UpdateDonorRequest`. - `WMDE\Fundraising\Frontend\Presentation\DonationMembershipApplicationAdapter` needs to take the two new fields into account for prepopulating the membership application form. - Unit tests should check for the additional fields.

NOTE: this involves **database changes** so all forms can support this change (address change (uses prefill), new donation, new membership ) ticket https://phabricator.wikimedia.org/T369158 should be done first This ticket is about chaning the `fundraising-application` and use the new changes from the bounded contexts. **Acceptance Criteria** - The donation related code can accept and process street name and house number. **Implementation notes** - create 2 new database columns for street name and house number (don't delete the "legacy" street column) - that means: - write a new migration for adding the new columns - in fundraising-donations: - `AddDonationController` (->every controller we have that takes in data for a new address donation) needs to be able to retrieve the fields `streetName` and `houseNumber` and put it into the request. - `DonationConfirmationPresenter` needs to output the two new fields. - `Api\UpdateDonorController` needs to pass the two new fields to the `UpdateDonorRequest`. - `WMDE\Fundraising\Frontend\Presentation\DonationMembershipApplicationAdapter` needs to take the two new fields into account for prepopulating the membership application form. - Unit tests should check for the additional fields.