Remove Payment data storage from data blob
Open, Needs TriagePublic
Actions

Assigned To

None

Authored By

	gabriel-wmde
	Mar 12 2024, 2:27 PM

Description

Acceptance Criteria

Implementation Details
When no code in the Fundraising Operation Center uses the legacy payment data in the data blob (see T320781: Use new payment tables in Fundraising Operation Center), do the following steps:

Remove calls to GetPaymentUseCase::getLegacyPaymentDataObject and Payment::getLegacyData from the memberships bounded context. Delete all tests that test the storage of legacy data.
Remove calls to GetPaymentUseCase::getLegacyPaymentDataObject and Payment::getLegacyData from the memberships bounded context. Delete all tests that test the storage of legacy data.
in the payment bounded context Delete the methods GetPaymentUseCase::getLegacyPaymentDataObject and Payment::getLegacyData (also in all inherited classes of Payment). Delete the LegacyPaymentData if it's still in there. Delete all tests that test the creation of the legacy data.
In the Fundraising application, change all tests that check for the existence of serialized payment data. Create new relases for the 3 the bounded contexts and create an integration branch, removing all errors

Status	Assigned	Task
Open	None	T203684 Improve code and architecture of Fundraising Operation Center
Open	None	T203654 Improve Code and Architecture of Fundraising Frontend
Open	None	T203679 Refactor fundraising database schema
Open	None	T192323 Improve expressiveness of Payment domain and reduce coupling
Open	None	T320781 Use new payment tables in Fundraising Operation Center
Open	None	T359941 Remove Payment data storage from data blob