[ECP-9559] Populate the shopper form fields of Oney 4X, 6X, 10X and 12X #2815
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
candemiralp
had a problem deploying
to
internal
GitHub Actions
Failure
|
SushmitaThakur
approved these changes
Nov 26, 2024
khushboo-singhvi
approved these changes
Nov 26, 2024
Merged
candemiralp
changed the title
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
Oney/Facilypay requires some additional information on the payment method component. However, the majority of this data overlaps with the information that the shopper fills out on shipping information page of the checkout.
Introducing missing custom method renderers modifies the component configuration object and pre-populates the form fields.
Tested scenarios