[dashboard] Better surface errors when Gitpod fails to get your Stripe subscription details #14180
Conversation
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
|
started the job as gitpod-build-jx-better-surface-subscription-errors.1 because the annotations in the pull request description changed |
…e subscription details
jankeromnes
force-pushed
the
jx/better-surface-subscription-errors
branch
from
dac504e to
3fcf430
Compare
|
Works! 🎉
|
jankeromnes
force-pushed
the
jx/better-surface-subscription-errors
branch
from
3fcf430 to
ab984d7
Compare
roboquat
added
deployed: webapp
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
In some rare edge cases, it can happen that Gitpod fails to get your Stripe subscription details (for example, one of these cases can be that a Stripe customer has two active Subscriptions for some reason, but there could exist other rare edge cases).
In these cases, Gitpod's backend throws an error. However, until now, the front-end only logged this error to the console, without showing it visibly in the UI. This PR fixes the latter, by visibly showing any such error message in the UI, so that users are at least aware that something went wrong.
Related Issue(s)
Fixes #14034
How to test
Release Notes
Documentation
Werft options:
If enabled this will build
install/previewValid options are
all,workspace,webapp,ide