-
Notifications
You must be signed in to change notification settings - Fork 219
feat(payments-next): Create Cancel churn page #19908
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
| 'churn-error-page-message-discount-already-applied', | ||
| { productName }, | ||
| `This discount was applied to a ${productName} subscription for your account. If you still need help, please contact our Support team.` | ||
| `This discount was applied to a ${productName} subscription for your account. If you still need help, contact our Support team.` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated as string in en.ftl is as follows:
churn-error-page-message-discount-already-applied = This discount was applied to a { $productName } subscription for your account. If you still need help, contact our Support team.
| enum ChurnCancelErrorReason { | ||
| AlreadyCanceling = 'already_canceling_at_period_end', | ||
| SubscriptionNotActive = 'subscription_not_active', | ||
| SubscriptionStillActive = 'subscription_still_active', | ||
| OfferExpired = 'no_churn_intervention_found', | ||
| GeneralError = 'general_error', | ||
| RedemptionLimitExceeded = 'redemption_limit_exceeded', | ||
| } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like this is never really used as an enum, just converted to an array of strings (and casted) below. I'd probably just switch this to an array of strings as const.
| return { | ||
| ...result, | ||
| cancelContent, | ||
| }; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[non-blocking] Imo we shouldn't combine return types like this. Instead return each separately.
return {
cancelChurnContentEligibility,
cancelFlowContent
}
This pull requests Adds the following churn pages and en.ftl: Error Not Found Cancel/component Updates ChurnInterventionService redeemCoupon to include churnType determineCancelChurnContentEligibility to include additional reasons (subscription_not_active, already_canceling_at_period_end, adds cmsOfferingContent when needed Updates SubscriptionManagementService to return subscription invoice information Closes PAY-3434
3802d41 to
0b10821
Compare
This pull request
Issue that this pull request solves
Closes: PAY-3434
Checklist
Put an
xin the boxes that applyScreenshots (Optional)
Reason: Eligible

Mobile
Tablet

Successfully redeemed

Mobile
Tablet

Reason: Already canceling

Mobile
Tablet

Reason: Discount already applied/Redemption limit exceeded

Mobile
Tablet

Reason: Subscription not active

Mobile
Tablet

Reason: No churn found

Mobile
Tablet
