fix(POM-360): enableThreeDS2 parameter encoding
#261
Merged
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
andrii-vysotskyi-cko
changed the title
enableThreeDS2 parameter encodingenableThreeDS2 parameter encoding
vitalii-vanziak-cko
approved these changes
Apr 9, 2024
andrii-vysotskyi-cko
deleted the
fix/POM-360/fix-enableThreeDS2-encoding
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.
Description
By default iOS encodes
let enableThreeDS2key as"enable_three_ds2"when strategy is set toconvertToSnakeCase. But backend expects it to beenable_three_d_s_2.Solution was to define custom
CodingKeys. In order to avoid re-defining all coding keysAutoCodingKeys.stenciltemplate was added.Jira Issue
https://checkout.atlassian.net/browse/POM-355