feat: Adjust UK Pi30 for regulatory changes#1338
Draft
judowning wants to merge 10 commits into
Draft
Conversation
- Add linkToProductList to GB Pay in 3 modal so the back-navigation link renders in the multi context, matching existing Pay in 30 Days behaviour - Update viewsShareAmount to accept account param; DEV_GB_MULTI uses subheadline assertion instead of calculator input (Pay in 30 Days has no calculator) - Pass account to viewsShareAmount in all four multiProduct test files
…30 and add stylings
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
3 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
This PR is intended to be merged after #1307 to adjust new Pi30 and product list modals to regulatory standards.
Screenshots / Videos
Testing instructions
Review
The expected SLA for reviews in this repo is days.
All pull requests require an initial review from your team followed by code owner approval.
While initial review is ongoing, please add the following label to your PR
Needs initial review. This initial review process should ensure that:Once you have received initial approval, please do the following:
Needs initial reviewNeeds codeowner reviewCode owners will then review the PR in accordance with our SLA. This process helps maintain code quality and reduces review cycles.