[Mobile Payments] Groundwork for refactor of CollectOrderPaymentUseCase #8184
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.
Part of: #8080
Description
This makes no functional changes, and the code added is not yet called.
I've duplicated the
CollectOrderPaymentUseCaseready for the planned refactor which will make Tap on Mobile easier. See pdfdoF-1My-p2 for full context.The existing use case has been renamed
LegacyCollectOrderPaymentUseCase, and when the refactor is complete and we switch over to it, this will be deleted.CollectOrderPaymentUseCaseis now the go-forward class, and I'll perform the refactor there and in other related files.Testing instructions
Check that unit tests pass, and that you can still take a Card Present payment.
RELEASE-NOTES.txtif necessary.