-
Notifications
You must be signed in to change notification settings - Fork 2k
feat: upgrade and downgrade confirmation modals #39275
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
Conversation
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.
10 files reviewed, 2 comments
|
Size Change: -2.19 kB (-0.07%) Total Size: 3.05 MB
|
📸 UI snapshots have been updated2 snapshot changes in total. 0 added, 2 modified, 0 deleted:
Triggered by this commit. |
| <CreateProjectModal isVisible={isCreateProjectModalShown} onClose={hideCreateProjectModal} /> | ||
| <CreateEnvironmentModal isVisible={isCreateEnvironmentModalShown} onClose={hideCreateEnvironmentModal} /> | ||
| <UpgradeModal /> | ||
| <ConfirmUpgradeModal /> |
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.
I don't think you can remove this because it may be used in onboarding so it needs to be mounted here. You should confirm.
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.
Double-checked, the global ConfirmUpgradeModal is not used anymore.
Upgrade flow in the onboarding goes like this:
OnboardingUpgradeSteprendersPlanCards- "Unlock all features"click on
PlanCardscallsstartPaymentEntryFlow(payment modal)
09156b9 to
8a62a70
Compare
|
And added events for downgrade/upgrade clicks to calculate the funnel |
📸 UI snapshots have been updated8 snapshot changes in total. 0 added, 8 modified, 0 deleted:
Triggered by this commit. |
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.
I initially changed the formatting of proratedAmount to make it more readable, but in this case, users are charged without confirmation, might be better to show the exact amount. I'll revert that.
56b4054 to
7fa8880
Compare
📸 UI snapshots have been updated8 snapshot changes in total. 0 added, 8 modified, 0 deleted:
Triggered by this commit. |
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.
Nah, the border doesn't feel better when there's just one addon card. I'll revert and polish it later
7ffa596 to
4ed22fa
Compare
📸 UI snapshots have been updated2 snapshot changes in total. 0 added, 2 modified, 0 deleted:
Triggered by this commit. |

Problem
Building on top of #39131.
Subscription updates involve non-trivial calculations, so it's important to add a confirmation flow with clear communication about how much will be charged and when.
Changes
Confirmation Modals
ConfirmUpgradeModalto not confuse anyone.Prorated Amount Refactor
billingProductLogicselector.useMemowithgetProration()utility function, which was verbose and difficult to reuse.proratedAmountandunusedPlatformAddonAmount, so it's easier to show them in the modals.How did you test this code?
Locally
switch-subscription-planfeature flag (release toggle) is enabled