Open
Conversation
…into epic-tokenisation
…into epic-tokenisation
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.
This PR adds a saved-cards toggle to OPF checkout that is fully driven by Spartacus outlets, keeping the bulk of UI logic in the tokenisation layer rather than in checkout. A standalone
OpfTokenisationSavedCardsToggleComponentis registered on theOPF_CHECKOUT_BEFORE_PAYMENT_OPTIONSoutlet (position BEFORE) and consumes a minimal outlet context fromOpfCheckoutPaymentsComponent(selectedPaymentId,savedCardsId,disabled, andsavedCardsSelected).The existing
OpfTokenisationCheckoutPaymentMethodComponentis also registered on the same outlet (position AFTER) and now reads the same outlet context to show the saved-cards list only when the toggle is selected. The checkout template was simplified to a singlecxOutlethost with this context and no longer uses ahasSavedCards$flag or local*ngIfaround the list. Finally, enums, imports, and module wiring were cleaned so outlet IDs are defined in checkout root and all saved-cards–related outlet registrations live in the tokenisation root module.