fix(POM-521): (Card Tokenization) Support multiple view component instances - #333
Merged
vitalii-vanziak-cko merged 2 commits intoOct 1, 2025
Merged
Conversation
andrii-vysotskyi-cko
approved these changes
Oct 1, 2025
vitalii-vanziak-cko
deleted the
fix/POM-521/card-view-component-instances
branch
October 1, 2025 12:02
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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
Issue:
POCardTokenizationViewComponentuses sharedPOEventDispatcher, so when multiple component instances are created they use the same event dispatcher, which causes all component's delegates to be notified about events, such asprocessTokenizedCard().Fix:
POCardTokenizationViewComponentcreates its own instance ofPOEventDispatcher, so events will be sent only to its delegate.POEventDispatcher.instance. Updated all usages.Jira Issue
https://checkout.atlassian.net/browse/POM-521