Feat [CHK-3619] Update mock api to support the new closePaymentResultError object #90
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
EmanueleBVtech
commented
Dec 10, 2024
EmanueleBVtech
commented
Dec 10, 2024
Merged
5 tasks
EmanueleBVtech
requested review from
ciuffagianluca,
pietro-tota,
CianoDanilo and
scaminati-bv
pietro-tota
reviewed
Dec 17, 2024
|
🎉 All dependencies have been resolved ! |
pietro-tota
deleted the
CHK-3619-update-be-mock-with-new-closepayment-error-object
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
depends on pagopa/pagopa-infra#2644
List of Changes
Added support on mock api GET transactions for the new closePaymentResultError object
Motivation and Context
This is part of a bigger effort aiming to have a proper mapping for closePayment errors in the whole platform
How Has This Been Tested?
Manual testing
Screenshots (if appropriate):
Types of changes
Checklist: