npm - @saasquatch/mint-components - Versions diffs - 2.2.0-2 → 2.2.0-4 - Mend

@saasquatch/mint-components 2.2.0-2 → 2.2.0-4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (63) hide show

package/dist/cjs/sqm-stencilbook.cjs.entry.js CHANGED Viewed

@@ -39,7 +39,7 @@ const sqmUserInfoFormView = require('./sqm-user-info-form-view-f1127a60.js');
 const utils = require('./utils-a8e0bd9b.js');
 const sqmLeadInputFieldView = require('./sqm-lead-input-field-view-818d9e9a.js');
 require('./data-6b5095f8.js');
-const sqmPartnerInfoModalView = require('./sqm-partner-info-modal-view-431ff976.js');
+const sqmPartnerInfoModalView = require('./sqm-partner-info-modal-view-2a3438e5.js');
 /**
  * lodash (Custom Build) <https://lodash.com/>
@@ -10729,7 +10729,7 @@ const column = "@author:noah\n@owner:noah\nFeature: Referral Table User Column\n
 const date = "@author:noah\n@owner:noah\nFeature: Referral Table Date Column\n\n    Shows the date of each referral\n\n    Background:\n        Given the date column is included in the referral table\n\n    @motivating\n    @ui\n    Scenario Outline: The title of the date column is configurable\n        Given the \"column-title\" prop is set to <value>\n        Then the date column is shown with <columTitle>\n        Examples:\n            | value           | columnTitle     |\n            |                 | Date Converted  |\n            | My column title | My column title |\n\n    @motivating\n    Scenario Outline: A configurable date associated with the referral is shown for each referral\n        Given the \"date-shown\" prop is set to <dateType>\n        And referrals exist\n        Then for each referral the <referralDate> is shown in the table\n        And the date is localized to the users locale\n        Examples:\n            | dateType            | referralDate          |\n            | dateReferralStarted | date referral started |\n            | dateReferralPaid    | date referral paid    |\n            | dateReferralEnded   | date referral ended   |\n            | dateModerated       | date moderated        |\n            | dateUserModified    | date user modified    |\n            | dateConverted       | date converted        |\n            | dateModified        | date modified         |\n            |                     | date converted        |";
-const rewards = "@author:noah @owner:noah\nFeature: Referral Table Reward Column\n  Shows the reward associated with each referral\n\n  Background: \n    Given the status column is included in the referral table\n    And at least one referral exists\n\n\n\n  @motivating @ui\n  Scenario Outline: The referral reward and its status are shown for each referral\n    Then for each referral reward there exists a reward cell\n    And the reward type and value is displayed in the cell\n    And the status of each reward is displayed as a pill in the cell\n    And rewards of <status> have a <pillColour> pill with the text <statusText>\n\n    Examples: \n      | status                     | pillColour | statusText         |\n      | Available                  | success    | Available          |\n      | Pending                    | warning    | Pending            |\n      | Pending Fraud Review       | warning    | Pending            |\n      | Pending Tax Review         | warning    | Pending            |\n      | Pending New Tax Form       | warning    | Pending            |\n      | Pending Tax Submission     | warning    | Pending            |\n      | Pending Partner Creation   | warning    | Pending            |\n      | Cancelled                  | danger     | Cancelled          |\n      | Payout Overdue             | danger     | Payout Failed      |\n      | Payout Reversed            | danger     | Payout Cancelled   |\n      | Expired                    | danger     | Expired            |\n      | Denied                     | danger     | Denied             |\n      | Redeemed                   | primary    | Redeemed           |\n      | Payout Transferred         | primary    | Payout Approved    |\n      | Payout Not Yet Due         | primary    | Payout Approved    |\n      | Payout Processing          | primary    | Payment Processing |\n\n  @motivating\n  Scenario: The pending period of a referral reward is shown inside the pill if scheduled\n    Given a reward that is pending\n    And the reward has a scheduled date in the future\n    Then the status pill of the reward will contain the text \"Pending for <relativeTime>\"\n    And the date is localized to the user's locale\n\n    Examples: \n      | relativeTime |\n      | 2 days       |\n      | 1 week       |\n      | 3 months     |\n\n  @motivating\n  Scenario: The expiry date of a reward is shown in a secondary pill\n    Given a reward that is available\n    And the reward has a set expiry date\n    Then an additional info pill will appear next to the status pill with the text \"Expiring in <relativeTime>\"\n    And the date is localized to the user's locale\n\n    Examples: \n      | relativeTime |\n      | 2 days       |\n      | 1 week       |\n\n  @motivating @ui\n  Scenario Outline: Expanding the reward cell shows specific detailed status messages\n    When a reward cell is clicked\n    Then it expands to show the detail view\n    And if the reward status is <status>\n    Then the detail text displays <detailMessage>\n\n    Examples: Payout States\n      | status             | detailMessage                                                              |\n      | Payout Approved    | Processing until {date}. Payout is then scheduled based on your settings.  |\n      | Payout Failed      | Payout failed due to a fulfillment issue and is currently being retried.   |\n      | Payout Cancelled   | If you think this is a mistake, contact our Support team.                  |\n      | Processing         | Processing until {date}. Payout is then scheduled based on your settings.  |\n\n    Examples: Tax Compliance States\n      | status                   | detailMessage                                                      |\n      | Pending Tax Review       | Awaiting tax form review                                           |\n      | Pending New Tax Form     | Invalid tax form. Submit a new form to receive your rewards.       |\n      | Pending Tax Submission   | Submit your tax documents to receive your rewards                  |\n      | Pending Partner Creation | Complete your tax and cash payout setup to receive your rewards    |\n\n    Examples: Standard States\n      | status             | detailMessage       |\n      | Available          | Reward expiring on  |\n      | Cancelled          | Reward cancelled on |\n      | Pending            | Available on        |\n      | Pending Review     | Pending since       |\n      | Denied             | Denied on           |\n      | Expired            | Reward expired on   |\n      | Redeemed           | Redeemed            |\n\n  @motivating\n  Scenario: Fuel Tank codes are displayed in the expanded view\n    Given a reward has a Fuel Tank code\n    When the reward cell is clicked\n    Then the expanded details display the text \"Your code is\"\n    And the code <fuelTankCode> is displayed in bold\n\n  @motivating\n  Scenario: Fraud denial help text is displayed\n    Given a reward has been denied due to fraud\n    And the component has \"deniedHelpText\" configured\n    When the reward cell is clicked\n    Then the expanded details display the denied help text next to the denial date\n\n  @minutia\n  Scenario: Payout-related reward statuses are determined by the state of the Paid Funds Transfer\n    Given a reward exists\n    And the reward has a connected Paid Funds Transfer (PFT)\n    When the PFT is in <pftState>\n    Then the reward's status is <status>\n    And the status text displays <text>\n    And the status is displayed in a <pillColour> pill\n\n    Examples:\n      | pftState                                           | status              | text               | pillColour |\n      | transfer date is in the future | PROCESSING | Payment Processing | primary |\n      | successfully transferred to payment provider       | PAYOUT_TRANSFERRED  | Payout Approved    | primary    |\n      | approved but payout scheduled date not yet arrived | PAYOUT_NOT_YET_DUE  | Payout Approved    | primary    |\n      | failed due to fulfillment issue and retrying       | PAYOUT_OVERDUE      | Payout Failed      | danger     |\n      | reversed or cancelled after being processed        | PAYOUT_REVERSED     | Payout Cancelled   | danger     |\n";
+const rewards = "@author:noah @owner:noah\nFeature: Referral Table Reward Column\n  Shows the reward associated with each referral\n\n  Background:\n    Given the status column is included in the referral table\n    And at least one referral exists\n\n  @motivating\n  Scenario Outline: State precedence ladder\n    Given a reward, its referral's fraud state, and the user's tax connection\n    Then <rule> is produced\n    And the <resultingState>, <resultingBadgeText>, and <resultingDescriptionBody> is determined in the following <order>:\n\n    Examples:\n      | order | rule                                                                                                                                                                               | resultingState           | resultingBadgeText                                                         | resultingDescriptionBody                                                       |\n      |     1 | referral.fraudData.moderationStatus is \"DENIED\"                                                                                                                                    | DENIED                   | Denied                                                                     | Denied on Jan 1, 2026. Contact support.                                        |\n      |     2 | referral.fraudData.moderationStatus is \"PENDING\"                                                                                                                                   | PENDING_REVIEW           | Pending                                                                    | Pending since Jan 1, 2026                                                      |\n      |     3 | reward.rewardedCash is true AND impactConnection is NOT connected                                                                                                                  | PENDING_PARTNER_CREATION | Pending                                                                    | Complete your tax and cash payout setup to receive your rewards                |\n      |     4 | reward.rewardedCash is true AND impactConnection is connected AND publisher.withdrawalSettings is missing                                                                          | PENDING_PARTNER_CREATION | Pending                                                                    | Complete your tax and cash payout setup to receive your rewards                |\n      |     5 | partnerFundsTransfer.status is \"REVERSED\"                                                                                                                                          | PAYOUT_CANCELLED         | Payout Cancelled                                                           | If you think this is a mistake, contact our Support team.                      |\n      |     6 | partnerFundsTransfer.status is \"OVERDUE\"                                                                                                                                           | PAYOUT_FAILED            | Payout Failed                                                              | Payout failed due to a fulfillment issue and is currently being retried.       |\n      |     7 | partnerFundsTransfer.dateScheduled is in the future                                                                                                                                | PROCESSING               | Payment Processing                                                         | Processing until Jan 1, 2026. Payout is then scheduled based on your settings. |\n      |     8 | partnerFundsTransfer.status is \"TRANSFERRED\" / \"NOT_YET_DUE\", or dateScheduled has passed without REVERSED/OVERDUE                                                                 | PAYOUT_APPROVED          | Payout Approved                                                            | Processing until Jan 1, 2026. Payout is then scheduled based on your settings. |\n      |     9 | reward.pendingReasons includes \"US_TAX\" AND impactConnection.taxHandlingEnabled is false                                                                                           | PENDING                  | Pending                                                                    | Available on Jan 1, 2026 (if dateScheduledFor set; else no body line)          |\n      |    10 | reward.pendingReasons includes \"US_TAX\" AND impactConnection.connected is false                                                                                                    | PENDING_PARTNER_CREATION | Pending                                                                    | Complete your tax and cash payout setup to receive your rewards                |\n      |    11 | reward.pendingReasons includes \"US_TAX\" AND publisher.requiredTaxDocumentType is set AND publisher.currentTaxDocument is missing                                                   | PENDING_TAX_SUBMISSION   | Pending                                                                    | Submit your tax documents to receive your rewards                              |\n      |    12 | reward.pendingReasons includes \"US_TAX\" AND publisher.currentTaxDocument.status is \"INACTIVE\" / \"INVALID_W9_ELECTRONIC_DOCUMENT\" / \"INVALID_W9_ELECTRONIC_DOCUMENT_CHECK_INTERNAL\" | PENDING_NEW_TAX_FORM     | Pending                                                                    | Invalid tax form. Submit a new form to receive your rewards.                   |\n      |    13 | reward.pendingReasons includes \"US_TAX\" AND publisher.currentTaxDocument.status is \"NOT_VERIFIED\"                                                                                  | PENDING_TAX_REVIEW       | Pending                                                                    | Awaiting tax form review                                                       |\n      |    14 | reward.pendingReasons includes \"US_TAX\" AND publisher.currentTaxDocument.status is \"ACTIVE\" AND publisher.withdrawalSettings missing                                               | PENDING_PARTNER_CREATION | Pending                                                                    | Complete your tax and cash payout setup to receive your rewards                |\n      |    15 | reward.pendingReasons includes \"MISSING_PAYOUT_CONFIGURATION\"                                                                                                                      | PENDING_PARTNER_CREATION | Pending                                                                    | Complete your tax and cash payout setup to receive your rewards                |\n      |    16 | statuses includes \"REDEEMED\"                                                                                                                                                       | REDEEMED                 | Redeemed                                                                   | (no state-specific body line)                                                  |\n      |    17 | statuses includes \"CANCELLED\"                                                                                                                                                      | CANCELLED                | Cancelled                                                                  | Reward cancelled on Jan 1, 2026                                                |\n      |    18 | statuses includes \"EXPIRED\"                                                                                                                                                        | EXPIRED                  | Expired                                                                    | Reward expired on Jan 1, 2026                                                  |\n      |    19 | statuses includes \"PENDING\"                                                                                                                                                        | PENDING                  | Pending  (or \"Pending for {date}\" overlay if dateScheduledFor set)         | Available on Jan 1, 2026 (if dateScheduledFor set; else no body line)          |\n      |    20 | statuses includes \"AVAILABLE\"                                                                                                                                                      | AVAILABLE                | Available  (plus info pill \"{expiringText} {relative}\" if dateExpires set) | Reward expiring on Jan 1, 2026                                                 |\n\n  @motivating @ui\n  Scenario Outline: The referral reward and its status are shown for each referral\n    Then for each referral reward there exists a reward cell\n    And the reward type and value is displayed in the cell\n    And the status of each reward is displayed as a pill in the cell\n    And rewards of <status> have a <pillColour> pill with the text <statusText>\n\n    Examples:\n      | status                   | pillColour | statusText         |\n      | Available                | success    | Available          |\n      | Pending                  | warning    | Pending            |\n      | Pending Fraud Review     | warning    | Pending            |\n      | Pending Tax Review       | warning    | Pending            |\n      | Pending New Tax Form     | warning    | Pending            |\n      | Pending Tax Submission   | warning    | Pending            |\n      | Pending Partner Creation | warning    | Pending            |\n      | Cancelled                | danger     | Cancelled          |\n      | Payout Overdue           | danger     | Payout Failed      |\n      | Payout Reversed          | danger     | Payout Cancelled   |\n      | Expired                  | danger     | Expired            |\n      | Denied                   | danger     | Denied             |\n      | Redeemed                 | primary    | Redeemed           |\n      | Payout Transferred       | primary    | Payout Approved    |\n      | Payout Not Yet Due       | primary    | Payout Approved    |\n      | Payout Processing        | primary    | Payment Processing |\n\n  @motivating\n  Scenario: The pending period of a referral reward is shown inside the pill if scheduled\n    Given a reward that is pending\n    And the reward has a scheduled date in the future\n    Then the status pill of the reward will contain the text \"Pending for <relativeTime>\"\n    And the date is localized to the user's locale\n\n    Examples:\n      | relativeTime |\n      |       2 days |\n      |       1 week |\n      |     3 months |\n\n  @motivating\n  Scenario: The expiry date of a reward is shown in a secondary pill\n    Given a reward that is available\n    And the reward has a set expiry date\n    Then an additional info pill will appear next to the status pill with the text \"Expiring in <relativeTime>\"\n    And the date is localized to the user's locale\n\n    Examples:\n      | relativeTime |\n      |       2 days |\n      |       1 week |\n\n  @motivating @ui\n  Scenario Outline: Expanding the reward cell shows specific detailed status messages\n    When a reward cell is clicked\n    Then it expands to show the detail view\n    And if the reward status is <status>\n    Then the detail text displays <detailMessage>\n\n    Examples: Payout States\n      | status           | detailMessage                                                             |\n      | Payout Approved  | Processing until {date}. Payout is then scheduled based on your settings. |\n      | Payout Failed    | Payout failed due to a fulfillment issue and is currently being retried.  |\n      | Payout Cancelled | If you think this is a mistake, contact our Support team.                 |\n      | Processing       | Processing until {date}. Payout is then scheduled based on your settings. |\n\n    Examples: Tax Compliance States\n      | status                   | detailMessage                                                   |\n      | Pending Tax Review       | Awaiting tax form review                                        |\n      | Pending New Tax Form     | Invalid tax form. Submit a new form to receive your rewards.    |\n      | Pending Tax Submission   | Submit your tax documents to receive your rewards               |\n      | Pending Partner Creation | Complete your tax and cash payout setup to receive your rewards |\n\n    Examples: Standard States\n      | status         | detailMessage       |\n      | Available      | Reward expiring on  |\n      | Cancelled      | Reward cancelled on |\n      | Pending        | Available on        |\n      | Pending Review | Pending since       |\n      | Denied         | Denied on           |\n      | Expired        | Reward expired on   |\n      | Redeemed       | Redeemed            |\n\n  @motivating\n  Scenario: Fuel Tank codes are displayed in the expanded view\n    Given a reward has a Fuel Tank code\n    When the reward cell is clicked\n    Then the expanded details display the text \"Your code is\"\n    And the code <fuelTankCode> is displayed in bold\n\n  @motivating\n  Scenario: Fraud denial help text is displayed\n    Given a reward has been denied due to fraud\n    And the component has \"deniedHelpText\" configured\n    When the reward cell is clicked\n    Then the expanded details display the denied help text next to the denial date\n\n  @minutia\n  Scenario: Payout-related reward statuses are determined by the state of the Paid Funds Transfer\n    Given a reward exists\n    And the reward has a connected Paid Funds Transfer (PFT)\n    When the PFT is in <pftState>\n    Then the reward's status is <status>\n    And the status text displays <text>\n    And the status is displayed in a <pillColour> pill\n\n    Examples:\n      | pftState                                           | status             | text               | pillColour |\n      | transfer date is in the future                     | PROCESSING         | Payment Processing | primary    |\n      | successfully transferred to payment provider       | PAYOUT_TRANSFERRED | Payout Approved    | primary    |\n      | approved but payout scheduled date not yet arrived | PAYOUT_NOT_YET_DUE | Payout Approved    | primary    |\n      | failed due to fulfillment issue and retrying       | PAYOUT_OVERDUE     | Payout Failed      | danger     |\n      | reversed or cancelled after being processed        | PAYOUT_REVERSED    | Payout Cancelled   | danger     |\n";
 const status = "@author:noah\n@owner:noah\nFeature: Referral Table Status Column\n\n  Shows the status of each referral\n\n  Background:\n    Given the status column is included in the referral table\n\n  @motivating\n  @ui\n  Scenario: The title of the date column is configurable\n    Given the \"column-title\" prop is set to \"My column title\"\n    Then the date column is shown with \"My column title\"\n\n  @motivating\n  Scenario: The status column's fraudStatus maps to the fraud status of the referral\n    Given at least one referral\n    Then the referral cell fraud status is set to `moderationStatus` of the referral\n\n  @motivating\n  Scenario Outline: The status column displays the status of each referral\n    Given referrals exist\n    Then the status of each referral is displayed\n    And the status <status> is displayed as text from <statusTextProp> in a <pillColour> pill\n\n    Examples:\n      | status      | statusTextProp          | pillColour |\n      | In Progress | inProgressStatusText    | Orange     |\n      | Converted   | convertedStatusText     | Green      |\n      | Pending     | pendingReviewStatusText | Orange     |\n      | Denied      | deniedStatusText        | Red        |\n";
@@ -12511,7 +12511,7 @@ const scenario2 = "@author:derek\n@owner:derek\nFeature: Reward Table reward Col
 const scenario4 = "@author:derek @owner:derek\nFeature: Reward Table Source Column\n  Shows the source of each reward\n\n  @motivating @ui\n  Scenario Outline: The title of the source column is configurable\n    Given the \"column-title\" prop is set to <value>\n    Then the source column is shown with <columnTitle>\n\n    Examples:\n      | value           | columnTitle     |\n      | Source          |                 |\n      | My column title | My column title |\n\n  @motivating @ui\n  Scenario: The source column displays manual if the reward is caused by a manual action\n    Given a user with a \"MANUAL\" reward\n    When they view the rewards table\n    Then the source of their reward is displayed as \"Manual\"\n\n  @motivating @ui\n  Scenario: The source column displays the program name if the reward is caused automatically by a program\n    Given a user with a \"AUTOMATED\" program reward\n    And the program has name \"Loyalty Program\"\n    When they view the rewards table\n    Then the source of their reward is displayed as \"Loyalty Program\"\n\n  @motivating @ui\n  Scenario Outline: The source column displays customizable reward exchange text with amount if the reward is caused by reward exchange\n    Given the \"reward-exchange-text\" prop is <propValue>\n    And a user with a \"MANUAL\" reward\n    But it was created by a reward exchange\n    Then they view the rewards table\n    Then the source displays <exchangeText>\n    And under it displays the following\n      | prettyRedeemedCredit → prettyValue |\n\n    Examples:\n      | propValue | exchangeText    |\n      |           | Reward Exchange |\n      | Exchanged | Exchanged       |\n\n  @motivating @ui\n  Scenario Outline: The source column displays customizable referral information if the reward is from a referral\n    Given the \"reward-source-text\" prop is <propValue>\n    And a user with a referral reward\n    And that reward has <rewardSource>\n    When they view the rewards table\n    Then then source displays <referralText>\n    And under it displays the full name of the <referralUser>\n\n    Examples:\n      | propValue                                                                             | rewardSource  | referralText | referralUser  |\n      |                                                                                       | REFERRED      | Referred by  | referrer user |\n      |                                                                                       | FRIEND_SIGNUP | Referral to  | referred user |\n      | {rewardSource, select, FRIEND_SIGNUP {You Referred} REFERRED {Referred you} other {}} | REFERRED      | Referred you | referrer user |\n      | {rewardSource, select, FRIEND_SIGNUP {You Referred} REFERRED {Referred you} other {}} | FRIEND_SIGNUP | You Referred | referred user |\n\n  @motivating @ui\n  Scenario Outline: The source column displays the existing name for a referral if either the first name or last name does not exist\n    Given a user with a referral reward\n    And referral user exists\n    And referral user has <name>\n    But referral user has no <otherName>\n    When they view the rewards table\n    Then referral user's name is displayed as <name>\n\n    Examples:\n      | name       | otherName  |\n      | first.name | last.name  |\n      | last.name  | first.name |\n\n  @motivating @ui\n  Scenario Outline: The source column displays referral as \"Your Friend\" if the referral user has no names\n    Given a user with a referral reward\n    And that reward has <rewardSource>\n    And the <referralUser> has no first name\n    And the <referralUser> has no last name\n    When they view the rewards table\n    Then then source displays <sourceText>\n    And under it displays \"Your Friend\"\n\n    Examples:\n      | rewardSource  | referralUser  | sourceText  |\n      | FRIEND_SIGNUP | referrer      | Referral to |\n      | REFERRED      | referred user | Referred by |\n\n  @motivating @ui\n  Scenario Outline: The source column displays referral as \"Deleted User\" if the referral user is deleted in the system\n    Given a user with a referral reward\n    And that reward has <rewardSource>\n    But <referral> user was deleted\n    When they view the rewards table\n    Then the source displays <sourceText>\n    And under it displays \"Deleted User\"\n\n    Examples:\n      | rewardSource    | referral | sourceText  |\n      | \"FRIEND_SIGNUP\" | referrer | Referral to |\n      | \"REFERRED\"      | referred | Referred by |\n\n  @motivating @ui\n  Scenario Outline: The source column displays referral as \"Deleted referral\" if the referral user is deleted in the system\n    Given a user with a referral reward\n    And that reward has <rewardSource>\n    But <referral> user was deleted\n    When they view the rewards table\n    Then the source displays <sourceText>\n    And under it displays \"Deleted referral\"\n\n    Examples:\n      | rewardSource    | referral | sourceText  |\n      | \"FRIEND_SIGNUP\" | referrer | Referral to |\n      | \"REFERRED\"      | referred | Referred by |\n\n  @minutia @ui\n  Scenario Outline: Name fallbacks for referral users without names are customizable\n    Given <prop> with <value>\n    And a user with a referral reward\n    But the referral user <hadAction>\n    When they view the rewards table\n    Then the source displays <value> as the referral user\n\n    Examples:\n      | prop           | value           | hadAction                       |\n      | deleted-user   | Former Customer | was deleted                     |\n      | anonymous-user | Nameless User   | had first and last name deleted |\n\n  @motivating\n  Scenario Outline: Source text can be customized\n    Given the \"reward-source-text\" prop is \"{rewardSource, select, MANUAL {Support} AUTOMATED {Loyalty Program} other {}}\"\n    And a user with a <rewardSource> reward\n    When they view the rewards table\n    Then the source is <sourceText>\n\n    Examples:\n      | rewardSource | sourceText      |\n      | MANUAL       | Support         |\n      | AUTOMATED    | Loyalty Program |\n";
-const scenario3 = "@author:derek @owner:derek\nFeature: Reward Table Status Column\n  Shows the status of each reward\n\n  Background:\n    Given the status column is included in the reward table\n\n  @motivating @ui\n  Scenario Outline: The title of the status column is configurable\n    Given the \"column-title\" prop is set to <value>\n    Then the status column is shown with <columnTitle>\n\n    Examples:\n      | value           | columnTitle     |\n      | Status          |                 |\n      | My column title | My column title |\n\n  @motivating @ui\n  Scenario Outline: The status column displays the status of each reward\n    Given a user\n    And they have a <status> reward\n    When they view the reward table\n    Then the status of their reward is displayed in <pillColour> pill with <text>\n\n    Examples:\n      | status                   | text             | pillColour |\n      | AVAILABLE                | Available        | success    |\n      | CANCELLED                | Cancelled        | danger     |\n      | PENDING                  | Pending          | warning    |\n      | EXPIRED                  | Expired          | danger     |\n      | REDEEMED                 | Redeemed         | primary    |\n      | PENDING_REVIEW           | Pending          | warning    |\n      | PAYOUT_TRANSFERRED       | Payout Approved  | primary    |\n      | PAYOUT_NOT_YET_DUE       | Payout Approved  | primary    |\n      | PAYOUT_OVERDUE           | Payout Failed    | danger     |\n      | PAYOUT_REVERSED          | Payout Cancelled | danger     |\n      | PROCESSING               | Processing       | warning    |\n      | PENDING_TAX_REVIEW       | Pending          | warning    |\n      | PENDING_NEW_TAX_FORM     | Pending          | warning    |\n      | PENDING_TAX_SUBMISSION   | Pending          | warning    |\n      | PENDING_PARTNER_CREATION | Pending          | warning    |\n      | DENIED                   | Denied           | danger     |\n\n  @motivating\n  Scenario Outline: Reward status related information is displayed under status pills\n    Given a user\n    And they have a <reward>\n    And their program is\n    When they view the reward table\n    Then they see their reward\n    And under the pill is <text>\n    And the date is localized to the users locale\n\n    Examples: Standard Rewards\n      | reward                               | text                     |\n      | available reward with an expiry date | Expires <localized date> |\n      | redeemed reward                      | <localized date>         |\n      | expired reward                       | <localized date>         |\n      | cancelled reward                     | <localized date>         |\n      | pending reward with a scheduled date | Until <localized date>   |\n\n    Examples: Tax & Payout Rewards\n      | reward                                                       | text                                                                                |\n      | pending reward due to W9                                     | W-9 required                                                                        |\n      | pending reward due to fulfillment error                      | Fulfillment error                                                                   |\n      | reward pending review of referral                            | Awaiting review                                                                     |\n      | pending reward due to no connected Impact partner            | Complete your tax and cash payout setup to receive your rewards.                    |\n      | pending reward due to an invalid tax document                | Invalid tax form. Submit a new form to receive your rewards.                        |\n      | pending reward due to user required to submit a tax document | Submit your tax documents to receive your rewards.                                  |\n      | pending reward due to tax document being in review           | Awaiting tax form review.                                                           |\n      | reward whose payout is processing                            | Processing until <localized date>. Payout is then scheduled based on your settings. |\n      | reward whose payout failed                                   | Payout failed due to a fulfillment issue and is currently being retried.            |\n      | reward whose payout was approved                             | Payout approved and scheduled for payment based on your settings.                   |\n      | reward whose payout was cancelled                            | If you think this is a mistake, contact our Support team.                           |\n      | cancelled reward from denied referral                        | Detected self-referral                                                              |\n\n  @minutia\n  Scenario Outline: Tax-related reward statuses are based on the user's Impact tax connection\n    Given a user\n    And they are in a program that has Impact tax handling enabled\n    And they have at least one pending reward\n    And the reward's pending reasons include \"MISSING_PAYOUT_CONFIGURATION\"\n    Then the status description will be\n      \"\"\"\n      Complete your tax and cash payout setup to receive your rewards.\n      \"\"\"\n\n  @motivating\n  Scenario Outline: Statuses can be customized via ICU format\n    Given the \"status-text\" prop is \"{status, select, AVAILABLE {Redeem me!} CANCELLED {Unavailable} PENDING {Coming soon!} EXPIRED {Past due} REDEEMED {Spent} PENDING_REVIEW {Pending Review!} PAYOUT_SENT {Payout Sent!} PAYOUT_FAILED {Payout Failed!} PENDING_TAX_REVIEW {Pending Tax Review!} PENDING_NEW_TAX_FORM {Pending new tax form!} PENDING_TAX_SUBMISSION {Pending tax submission!} PENDING_PARTNER_CREATION {Pending partner creation!} DENIED {Unlucky!}}\"\n    And a user\n    And they have a <status> reward\n    When they view the reward table\n    Then the status of their reward is displayed in <pillColour> pill with <text>\n\n    Examples:\n      | status             | text              | pillColour |\n      | AVAILABLE          | Redeem me!        | success    |\n      | CANCELLED          | Unavailable       | danger     |\n      | PENDING            | Coming soon!      | warning    |\n      | EXPIRED            | Past due          | danger     |\n      | REDEEMED           | Spent             | primary    |\n      | PENDING_REVIEW     | Pending Review!   | warning    |\n      | PAYOUT_TRANSFERRED | Payout Approved!  | primary    |\n      | PAYOUT_NOT_YET_DUE | Payout Approved!  | primary    |\n      | PAYOUT_OVERDUE     | Payout Failed!    | danger     |\n      | PAYOUT_REVERSED    | Payout Cancelled! | danger     |\n      | DENIED             | Unlucky!          | danger     |\n\n  @minutia @ui\n  Scenario Outline: Expiry status date text can be configured\n    Given the \"expiry-text\" prop has <value>\n    And a user with an available reward with an expiry date\n    When they view the reward table\n    Then they see <text> under the Available Status pill\n\n    Examples:\n      | value         | text                           |\n      | Expires       | Expires <localized date>       |\n      | Redeem before | Redeem before <localized date> |\n\n  @motivating\n  Scenario: Payout-related reward statuses are determined by the state of the Paid Funds Transfer\n    Given a user has a reward with a connected Paid Funds Transfer (PFT)\n    When the PFT is in <pftState>\n    Then the reward's status is <status>\n    And the status is displayed in a <pillColour> pill with <text>\n    And under the pill is <description>\n\n    Examples:\n      | pftState                                           | status             | text             | pillColour | description                                                                         |\n      | transfer date is in the future                     | PROCESSING         | Processing       | warning    | Processing until <localized date>. Payout is then scheduled based on your settings. |\n      | successfully transferred to payment provider       | PAYOUT_TRANSFERRED | Payout Approved  | primary    | Payout approved and scheduled for payment based on your settings.                   |\n      | approved but payout scheduled date not yet arrived | PAYOUT_NOT_YET_DUE | Payout Approved  | primary    | Payout approved and scheduled for payment based on your settings.                   |\n      | failed due to fulfillment issue and retrying       | PAYOUT_OVERDUE     | Payout Failed    | danger     | Payout failed due to a fulfillment issue and is currently being retried.            |\n      | reversed or cancelled after being processed        | PAYOUT_REVERSED    | Payout Cancelled | danger     | If you think this is a mistake, contact our Support team.                           |\n";
+const scenario3 = "@author:derek @owner:derek\nFeature: Reward Table Status Column\n  Shows the status of each reward\n\n  Background:\n    Given the status column is included in the reward table\n\n  @motivating @ui\n  Scenario Outline: The title of the status column is configurable\n    Given the \"column-title\" prop is set to <value>\n    Then the status column is shown with <columnTitle>\n\n    Examples:\n      | value           | columnTitle     |\n      | Status          |                 |\n      | My column title | My column title |\n\n  @motivating @ui\n  Scenario Outline: The status column displays the status of each reward\n    Given a user\n    And they have a <status> reward\n    When they view the reward table\n    Then the status of their reward is displayed in <pillColour> pill with <text>\n\n    Examples:\n      | status                   | text             | pillColour |\n      | AVAILABLE                | Available        | success    |\n      | CANCELLED                | Cancelled        | danger     |\n      | PENDING                  | Pending          | warning    |\n      | EXPIRED                  | Expired          | danger     |\n      | REDEEMED                 | Redeemed         | primary    |\n      | PENDING_REVIEW           | Pending          | warning    |\n      | PAYOUT_TRANSFERRED       | Payout Approved  | primary    |\n      | PAYOUT_NOT_YET_DUE       | Payout Approved  | primary    |\n      | PAYOUT_OVERDUE           | Payout Failed    | danger     |\n      | PAYOUT_REVERSED          | Payout Cancelled | danger     |\n      | PROCESSING               | Processing       | warning    |\n      | PENDING_TAX_REVIEW       | Pending          | warning    |\n      | PENDING_NEW_TAX_FORM     | Pending          | warning    |\n      | PENDING_TAX_SUBMISSION   | Pending          | warning    |\n      | PENDING_PARTNER_CREATION | Pending          | warning    |\n      | DENIED                   | Denied           | danger     |\n\n  @motivating\n  Scenario Outline: Status precedence ladder\n    Given a reward, its referral fraud state, the user's Impact tax connection\n    Then <rule> is produced\n    And the <resultingStatus>, <resultingBadgeText>, and <resultingDescription> is determined in the following <order>:\n\n    Examples:\n      | order | rule                                                                                                               | resultingStatus  | resultingBadgeText | resultingDescription                                                           |\n      |     1 | referral.fraudData.moderationStatus is \"DENIED\"                                                                    | DENIED           | Denied             | Detected self-referral                                                         |\n      |     2 | referral.fraudData.moderationStatus is \"PENDING\"                                                                   | PENDING_REVIEW   | Pending            | Awaiting review                                                                |\n      |     3 | reward.rewardedCash is true AND impactConnection is NOT connected                                                  | PENDING          | Pending            | Complete your cash payout setup to receive your rewards.                       |\n      |     4 | reward.rewardedCash is true AND impactConnection is connected AND publisher.withdrawalSettings is missing          | PENDING          | Pending            | Complete your cash payout setup to receive your rewards.                       |\n      |     5 | partnerFundsTransfer.status is \"REVERSED\"                                                                          | PAYOUT_CANCELLED | Payout Cancelled   | If you think this is a mistake, contact our Support team.                      |\n      |     6 | partnerFundsTransfer.status is \"OVERDUE\"                                                                           | PAYOUT_FAILED    | Payout Failed      | Payout failed due to a fulfillment issue and is currently being retried.       |\n      |     7 | reward.pendingReasons includes \"MISSING_PAYOUT_CONFIGURATION\" AND publisher.withdrawalSettings is missing          | PENDING          | Pending            | Complete your cash payout setup to receive your rewards.                       |\n      |     8 | partnerFundsTransfer.dateScheduled is in the future                                                                | PROCESSING       | Payment Processing | Processing until Jan 1, 2026. Payout is then scheduled based on your settings. |\n      |     9 | partnerFundsTransfer.status is \"TRANSFERRED\" / \"NOT_YET_DUE\", or dateScheduled has passed without REVERSED/OVERDUE | PAYOUT_APPROVED  | Payout Approved    | Payout approved and scheduled for payment based on your settings.              |\n      |    10 | reward.dateCancelled is set                                                                                        | CANCELLED        | Cancelled          | Jan 1, 2026                                                                    |\n      |    11 | reward.statuses includes \"EXPIRED\"                                                                                 | EXPIRED          | Expired            | Jan 1, 2026                                                                    |\n      |    12 | reward.statuses includes \"PENDING\"                                                                                 | PENDING          | Pending            | Until Jan 1, 2026                                                              |\n      |    13 | statuses includes \"REDEEMED\"                                                                                       | REDEEMED         | Redeemed           | Jan 1, 2026                                                                    |\n      |    14 | statuses includes \"AVAILABLE\"                                                                                      | AVAILABLE        | Available          | Expires Jan 1, 2026                                                            |\n      |    15 | statuses includes \"CANCELLED\"                                                                                      | CANCELLED        | Cancelled          | Jan 1, 2026                                                                    |\n# This spec should probably be inserted in to the above spec after rule 9 because it gets invoked when the reward state is pending\n# and does not hit the rules that output pending from above\n\n  @motivating\n  Scenario Outline: PENDING description precedence ladder\n    Given a PENDING reward, its pendingReasons, and the user's Impact tax connection\n    Then <rule> is produced\n    And the <resultingStatus>, <resultingBadgeText>, and <resultingDescription> is determined in the following order:\n\n    Examples:\n      | order | rule                                                                                                                                    | resultingStatus | resultingBadgeText | resultingDescription                                             |\n      |     1 | pendingReasons includes \"US_TAX\" AND impactConnection.taxHandlingEnabled is false                                                       | PENDING         | Pending            | W-9 required                                                     |\n      |     2 | pendingReasons includes \"US_TAX\" AND impactConnection is NOT connected                                                                  | PENDING         | Pending            | Complete your tax and cash payout setup to receive your rewards. |\n      |     3 | pendingReasons includes \"US_TAX\" AND publisher.requiredTaxDocumentType is set AND publisher.currentTaxDocument is missing               | PENDING         | Pending            | Submit your tax documents to receive your rewards.               |\n      |     4 | pendingReasons includes \"US_TAX\" AND publisher.requiredTaxDocumentType is set AND publisher.currentTaxDocument.status is \"INACTIVE\"     | PENDING         | Pending            | Invalid tax form. Submit a new form to receive your rewards.     |\n      |     5 | pendingReasons includes \"US_TAX\" AND publisher.requiredTaxDocumentType is set AND publisher.currentTaxDocument.status is \"NOT_VERIFIED\" | PENDING         | Pending            | Awaiting tax form review.                                        |\n      |     6 | pendingReasons includes \"US_TAX\" AND publisher.withdrawalSettings is missing                                                            | PENDING         | Pending            | Complete your tax and cash payout setup to receive your rewards. |\n      |     7 | pendingReasons includes \"MISSING_PAYOUT_CONFIGURATION\"                                                                                  | PENDING         | Pending            | Complete your tax and cash payout setup to receive your rewards. |\n      |     8 | reward.rewardedCash is true AND impactConnection is NOT connected (fallback when no pendingReason returned)                             | PENDING         | Pending            | Complete your tax and cash payout setup to receive your rewards. |\n      |     9 | reward.rewardedCash is true AND impactConnection is connected AND publisher.withdrawalSettings is missing (fallback)                    | PENDING         | Pending            | Complete your tax and cash payout setup to receive your rewards. |\n\n  @motivating\n  Scenario Outline: Reward status related information is displayed under status pills\n    Given a user\n    And they have a <reward>\n    And their program is\n    When they view the reward table\n    Then they see their reward\n    And under the pill is <text>\n    And the date is localized to the users locale\n\n    Examples: Standard Rewards\n      | reward                               | text                     |\n      | available reward with an expiry date | Expires <localized date> |\n      | redeemed reward                      | <localized date>         |\n      | expired reward                       | <localized date>         |\n      | cancelled reward                     | <localized date>         |\n      | pending reward with a scheduled date | Until <localized date>   |\n\n    Examples: Tax & Payout Rewards\n      | reward                                                       | text                                                                                |\n      | pending reward due to W9                                     | W-9 required                                                                        |\n      | pending reward due to fulfillment error                      | Fulfillment error                                                                   |\n      | reward pending review of referral                            | Awaiting review                                                                     |\n      | pending reward due to no connected Impact partner            | Complete your tax and cash payout setup to receive your rewards.                    |\n      | pending reward due to an invalid tax document                | Invalid tax form. Submit a new form to receive your rewards.                        |\n      | pending reward due to user required to submit a tax document | Submit your tax documents to receive your rewards.                                  |\n      | pending reward due to tax document being in review           | Awaiting tax form review.                                                           |\n      | reward whose payout is processing                            | Processing until <localized date>. Payout is then scheduled based on your settings. |\n      | reward whose payout failed                                   | Payout failed due to a fulfillment issue and is currently being retried.            |\n      | reward whose payout was approved                             | Payout approved and scheduled for payment based on your settings.                   |\n      | reward whose payout was cancelled                            | If you think this is a mistake, contact our Support team.                           |\n      | cancelled reward from denied referral                        | Detected self-referral                                                              |\n\n  @minutia\n  Scenario Outline: Tax-related reward statuses are based on the user's Impact tax connection\n    Given a user\n    And they are in a program that has Impact tax handling enabled\n    And they have at least one pending reward\n    And the reward's pending reasons include \"MISSING_PAYOUT_CONFIGURATION\"\n    Then the status description will be\n      \"\"\"\n      Complete your tax and cash payout setup to receive your rewards.\n      \"\"\"\n\n  @motivating\n  Scenario Outline: Statuses can be customized via ICU format\n    Given the \"status-text\" prop is \"{status, select, AVAILABLE {Redeem me!} CANCELLED {Unavailable} PENDING {Coming soon!} EXPIRED {Past due} REDEEMED {Spent} PENDING_REVIEW {Pending Review!} PAYOUT_SENT {Payout Sent!} PAYOUT_FAILED {Payout Failed!} PENDING_TAX_REVIEW {Pending Tax Review!} PENDING_NEW_TAX_FORM {Pending new tax form!} PENDING_TAX_SUBMISSION {Pending tax submission!} PENDING_PARTNER_CREATION {Pending partner creation!} DENIED {Unlucky!}}\"\n    And a user\n    And they have a <status> reward\n    When they view the reward table\n    Then the status of their reward is displayed in <pillColour> pill with <text>\n\n    Examples:\n      | status             | text              | pillColour |\n      | AVAILABLE          | Redeem me!        | success    |\n      | CANCELLED          | Unavailable       | danger     |\n      | PENDING            | Coming soon!      | warning    |\n      | EXPIRED            | Past due          | danger     |\n      | REDEEMED           | Spent             | primary    |\n      | PENDING_REVIEW     | Pending Review!   | warning    |\n      | PAYOUT_TRANSFERRED | Payout Approved!  | primary    |\n      | PAYOUT_NOT_YET_DUE | Payout Approved!  | primary    |\n      | PAYOUT_OVERDUE     | Payout Failed!    | danger     |\n      | PAYOUT_REVERSED    | Payout Cancelled! | danger     |\n      | DENIED             | Unlucky!          | danger     |\n\n  @minutia @ui\n  Scenario Outline: Expiry status date text can be configured\n    Given the \"expiry-text\" prop has <value>\n    And a user with an available reward with an expiry date\n    When they view the reward table\n    Then they see <text> under the Available Status pill\n\n    Examples:\n      | value         | text                           |\n      | Expires       | Expires <localized date>       |\n      | Redeem before | Redeem before <localized date> |\n\n  @motivating\n  Scenario: Payout-related reward statuses are determined by the state of the Paid Funds Transfer\n    Given a user has a reward with a connected Paid Funds Transfer (PFT)\n    When the PFT is in <pftState>\n    Then the reward's status is <status>\n    And the status is displayed in a <pillColour> pill with <text>\n    And under the pill is <description>\n\n    Examples:\n      | pftState                                           | status             | text             | pillColour | description                                                                         |\n      | transfer date is in the future                     | PROCESSING         | Processing       | warning    | Processing until <localized date>. Payout is then scheduled based on your settings. |\n      | successfully transferred to payment provider       | PAYOUT_TRANSFERRED | Payout Approved  | primary    | Payout approved and scheduled for payment based on your settings.                   |\n      | approved but payout scheduled date not yet arrived | PAYOUT_NOT_YET_DUE | Payout Approved  | primary    | Payout approved and scheduled for payment based on your settings.                   |\n      | failed due to fulfillment issue and retrying       | PAYOUT_OVERDUE     | Payout Failed    | danger     | Payout failed due to a fulfillment issue and is currently being retried.            |\n      | reversed or cancelled after being processed        | PAYOUT_REVERSED    | Payout Cancelled | danger     | If you think this is a mistake, contact our Support team.                           |\n";
 const scenario$x = scenario1 + scenario2 + scenario3 + scenario4;
 const RewardsTableCell_stories = {
@@ -18927,6 +18927,7 @@ const defaultText$1 = {
   descriptionNewPartner: "Confirm your country and currency now to get your future rewards faster.",
   descriptionExistingPartner: "We noticed you are already an Impact.com partner, please confirm your information.",
   supportDescriptionExistingPartner: "If this is a mistake, please contact Support or sign up for this referral program with a different email.",
+  supportLink: "Support",
   countryLabel: "Country",
   currencyLabel: "Currency",
   submitButtonLabel: "Submit",
@@ -19051,6 +19052,16 @@ const Closed = () => {
   };
   return index.h(sqmPartnerInfoModalView.PartnerInfoModalView, Object.assign({}, props));
 };
+const SQMComponentExistingPartner = () => {
+  return (index.h("sqm-partner-info-modal", { "support-link": "Support", "support-description-existing-partner": "If this is a mistake, please contact {supportLink} or sign up for this referral program with a different email.", "allow-banking-collection": "I have read the {termsAndConditionsLink} and allow impact.com to collect my tax and banking information", "terms-and-conditions-label": "terms and conditions", "terms-and-conditions-link": "https://terms.advocate.impact.com/PayoutTermsAndConditions.html", demoData: {
+      states: { open: true, isExistingPartner: true },
+    } }));
+};
+const SQMComponentNewPartner = () => {
+  return (index.h("sqm-partner-info-modal", { demoData: {
+      states: { open: true, isExistingPartner: false },
+    } }));
+};
 const PartnerInfoModal = /*#__PURE__*/Object.freeze({
   __proto__: null,
@@ -19063,7 +19074,9 @@ const PartnerInfoModal = /*#__PURE__*/Object.freeze({
   Submitting: Submitting,
   WithError: WithError$3,
   ValidationError: ValidationError$1,
-  Closed: Closed
+  Closed: Closed,
+  SQMComponentExistingPartner: SQMComponentExistingPartner,
+  SQMComponentNewPartner: SQMComponentNewPartner
 });
 const WidgetVerification_stories = {

package/dist/collection/components/sqm-partner-info-modal/PartnerInfoModal.stories.js CHANGED Viewed

@@ -34,6 +34,7 @@ const defaultText = {
   descriptionNewPartner: "Confirm your country and currency now to get your future rewards faster.",
   descriptionExistingPartner: "We noticed you are already an Impact.com partner, please confirm your information.",
   supportDescriptionExistingPartner: "If this is a mistake, please contact Support or sign up for this referral program with a different email.",
+  supportLink: "Support",
   countryLabel: "Country",
   currencyLabel: "Currency",
   submitButtonLabel: "Submit",
@@ -158,3 +159,13 @@ export const Closed = () => {
   };
   return h(PartnerInfoModalView, Object.assign({}, props));
 };
+export const SQMComponentExistingPartner = () => {
+  return (h("sqm-partner-info-modal", { "support-link": "Support", "support-description-existing-partner": "If this is a mistake, please contact {supportLink} or sign up for this referral program with a different email.", "allow-banking-collection": "I have read the {termsAndConditionsLink} and allow impact.com to collect my tax and banking information", "terms-and-conditions-label": "terms and conditions", "terms-and-conditions-link": "https://terms.advocate.impact.com/PayoutTermsAndConditions.html", demoData: {
+      states: { open: true, isExistingPartner: true },
+    } }));
+};
+export const SQMComponentNewPartner = () => {
+  return (h("sqm-partner-info-modal", { demoData: {
+      states: { open: true, isExistingPartner: false },
+    } }));
+};

package/dist/collection/components/sqm-partner-info-modal/sqm-partner-info-modal-view.js CHANGED Viewed

@@ -69,9 +69,15 @@ export function PartnerInfoModalContentView(props) {
   const { states, callbacks, text } = props;
   const sheet = createStyleSheet(style);
   const styleString = sheet.toString();
+  const supportMessage = intl.formatMessage({
+    id: "supportDescriptionExistingPartner",
+    defaultMessage: text.supportDescriptionExistingPartner,
+  }, {
+    supportLink: (h("a", { target: "_blank", href: `mailto:advocate-support@impact.com` }, text.supportLink)),
+  });
   const description = states.isExistingPartner ? (h("span", { class: sheet.classes.DescriptionContainer },
     h("p", null, text.descriptionExistingPartner),
-    h("p", null, text.supportDescriptionExistingPartner))) : (h("p", { class: sheet.classes.DescriptionContainer }, text.descriptionNewPartner));
+    h("p", null, supportMessage))) : (h("p", { class: sheet.classes.DescriptionContainer }, text.descriptionNewPartner));
   const buttonLabel = states.isExistingPartner
     ? text.confirmButtonLabel
     : text.submitButtonLabel;

package/dist/collection/components/sqm-partner-info-modal/sqm-partner-info-modal.js CHANGED Viewed

@@ -48,7 +48,13 @@ export class PartnerInfoModal {
      * @uiName Existing partner support description
      * @uiWidget textArea
      */
-    this.supportDescriptionExistingPartner = "If this is a mistake, please contact Support or sign up for this referral program with a different email.";
+    this.supportDescriptionExistingPartner = "If this is a mistake, please contact {supportLink} or sign up for this referral program with a different email.";
+    /**
+     * Support description for existing partner confirmation
+     *
+     * @uiName Existing partner support description
+     */
+    this.supportLink = "Support";
     /**
      * Edit the property called terms and conditions text to change what's displayed for {termsAndConditionsLink}.
      * @uiName Terms and conditions checkbox
@@ -247,7 +253,28 @@ export class PartnerInfoModal {
       },
       "attribute": "support-description-existing-partner",
       "reflect": false,
-      "defaultValue": "\"If this is a mistake, please contact Support or sign up for this referral program with a different email.\""
+      "defaultValue": "\"If this is a mistake, please contact {supportLink} or sign up for this referral program with a different email.\""
+    },
+    "supportLink": {
+      "type": "string",
+      "mutable": false,
+      "complexType": {
+        "original": "string",
+        "resolved": "string",
+        "references": {}
+      },
+      "required": false,
+      "optional": false,
+      "docs": {
+        "tags": [{
+            "text": "Existing partner support description",
+            "name": "uiName"
+          }],
+        "text": "Support description for existing partner confirmation"
+      },
+      "attribute": "support-link",
+      "reflect": false,
+      "defaultValue": "\"Support\""
     },
     "allowBankingCollection": {
       "type": "string",
@@ -635,6 +662,7 @@ function useDemoPartnerInfoModal(props) {
       searchCountryPlaceholder: props.searchCountryPlaceholder,
       searchCurrencyPlaceholder: props.searchCurrencyPlaceholder,
       supportDescriptionExistingPartner: props.supportDescriptionExistingPartner,
+      supportLink: props.supportLink,
       modalHeaderExistingPartner: props.modalHeaderExistingPartner,
     },
   }, props.demoData || stateOverride, { arrayMerge: (_, a) => a });

package/dist/collection/components/sqm-widget-verification/sqm-email-verification/useEmailVerification.js CHANGED Viewed

@@ -1,4 +1,4 @@
-import { useMutation, useParent, useQuery, useUserIdentity, } from "@saasquatch/component-boilerplate";
+import { useMutation, useQuery, useSetParent, useUserIdentity, } from "@saasquatch/component-boilerplate";
 import { useEffect, useState } from "@saasquatch/universal-hooks";
 import { gql } from "graphql-request";
 import { SHOW_CODE_NAMESPACE, VERIFICATION_EMAIL_NAMESPACE } from "../keys";
@@ -60,8 +60,12 @@ export function useUpsertUserEmail() {
   ];
 }
 export function useWidgetEmailVerification(props) {
-  const [_, setShowCode] = useParent(SHOW_CODE_NAMESPACE);
-  const [email, setEmail] = useParent(VERIFICATION_EMAIL_NAMESPACE);
+  // NOTE: useSetParent (not useParent) so that calling these setters is a
+  // no-op fallback instead of throwing TypeError when the parent provider
+  // hasn't connected yet (e.g. inside <sl-dialog> on first paint). Throwing
+  // here would skip setLoading(false) and leave the button stuck spinning.
+  const setShowCode = useSetParent(SHOW_CODE_NAMESPACE);
+  const setEmail = useSetParent(VERIFICATION_EMAIL_NAMESPACE);
   const [emailExists, setEmailExists] = useState(false);
   const [error, setError] = useState(false);
   const [mutationError, setMutationError] = useState(false);
@@ -80,29 +84,43 @@ export function useWidgetEmailVerification(props) {
       setLoading(false);
   }, [initialized]);
   const submitEmail = async (e) => {
+    var _a, _b, _c, _d;
     e.preventDefault();
     if (!(data === null || data === void 0 ? void 0 : data.viewer))
       return;
     setLoading(true);
-    const toAddress = data.viewer.email;
+    setMutationError(false);
+    setError(false);
+    // Resolve the address we'll actually verify. If the user already has an
+    // email on record, use it; otherwise pull the typed value from the form
+    // and upsert it. We capture this AFTER the upsert so the value we hand
+    // off to the code-verification step is never null.
+    let toAddress = data.viewer.email;
     if (!toAddress) {
-      // If no email on the user, set one
-      const formData = e.detail.formData;
-      const newEmail = formData.get("email").toString();
+      const formData = (_a = e.detail) === null || _a === void 0 ? void 0 : _a.formData;
+      const newEmail = (_c = (_b = formData === null || formData === void 0 ? void 0 : formData.get("email")) === null || _b === void 0 ? void 0 : _b.toString()) !== null && _c !== void 0 ? _c : "";
       if (!emailRegex.test(newEmail)) {
         setError(true);
+        setLoading(false);
         return;
       }
-      const result = await upsertUserEmail(newEmail);
-      if (!result || !result.user.email)
+      const upsertResult = await upsertUserEmail(newEmail);
+      if (!upsertResult || !((_d = upsertResult.upsertUser) === null || _d === void 0 ? void 0 : _d.email)) {
         setError(true);
+        setLoading(false);
+        return;
+      }
+      toAddress = upsertResult.upsertUser.email;
     }
     // UI should not allow this call til initialisation is done
-    if (!initialized)
+    if (!initialized) {
+      setLoading(false);
       return;
+    }
     const result = await sendEmail();
-    if (!result || !result.success)
+    if (!result || !result.success) {
       setMutationError(true);
+    }
     else {
       // This is used to let the code verification widget know an email was already sent
       setEmail(toAddress);

package/dist/collection/components/sqm-widget-verification/useWidgetVerification.js CHANGED Viewed

@@ -2,7 +2,7 @@ import { useLazyQuery, useParentState, useSetParent, } from "@saasquatch/compone
 import { useState } from "@saasquatch/stencil-hooks";
 import { useEffect } from "@saasquatch/universal-hooks";
 import { gql } from "graphql-request";
-import { PARTNER_CREATED_NAMESPACE, SHOW_CODE_NAMESPACE, SHOW_PARTNER_MODAL_NAMESPACE, VERIFICATION_PARENT_NAMESPACE, } from "./keys";
+import { PARTNER_CREATED_NAMESPACE, SHOW_CODE_NAMESPACE, SHOW_PARTNER_MODAL_NAMESPACE, VERIFICATION_EMAIL_NAMESPACE, VERIFICATION_PARENT_NAMESPACE, } from "./keys";
 const USER_LOOKUP = gql `
   query checkUserVerification {
     viewer {
@@ -27,6 +27,16 @@ export function useWidgetVerification() {
     namespace: SHOW_CODE_NAMESPACE,
     initialValue: false,
   });
+  // Register the verification-email namespace at the widget-verification
+  // host so that <sqm-email-verification> (writer) and <sqm-code-verification>
+  // (reader) can communicate. This registration was accidentally removed in
+  // commit cfbfad9 ("a bunch of review and cleanup of unused code"), which
+  // caused setEmail() in the email step to throw TypeError and aborted the
+  // rest of submitEmail before it could call setShowCode(true).
+  useParentState({
+    namespace: VERIFICATION_EMAIL_NAMESPACE,
+    initialValue: undefined,
+  });
   const setContext = useSetParent(VERIFICATION_PARENT_NAMESPACE);
   const [loading, setLoading] = useState(true);
   const [showPartnerModal, setShowPartnerModal] = useParentState({

package/dist/esm/{keys-d7c5c851.js → keys-1054056a.js} RENAMED Viewed

@@ -5,4 +5,4 @@ const VERIFICATION_EMAIL_NAMESPACE = "sq:verification-email";
 const VERIFICATION_PARENT_NAMESPACE = "sq:verification-context";
 const VERIFICATION_EVENT_KEY = "sq:code-verified";
-export { PARTNER_CREATED_NAMESPACE as P, SHOW_CODE_NAMESPACE as S, VERIFICATION_PARENT_NAMESPACE as V, SHOW_PARTNER_MODAL_NAMESPACE as a, VERIFICATION_EMAIL_NAMESPACE as b, VERIFICATION_EVENT_KEY as c };
+export { PARTNER_CREATED_NAMESPACE as P, SHOW_CODE_NAMESPACE as S, VERIFICATION_PARENT_NAMESPACE as V, VERIFICATION_EMAIL_NAMESPACE as a, SHOW_PARTNER_MODAL_NAMESPACE as b, VERIFICATION_EVENT_KEY as c };