[UBP] Extract common UBP configuration components #12732
Merged
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
2 tasks
svenefftinge
approved these changes
Sep 7, 2022
Not sure what happened there, but the follow up PR (#12733) that uses these components does have a preview env. |
17 tasks
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
Extract common React components that will be used on both the team settings and user settings pages to configure usage based pricing. Specifically:
and:
These components will be re-used in a later PR when they are added to the individual user settings page.
Related Issue(s)
Part of #12685
How to test
The setup should work correctly as before, with a new customer created in Stripe with the correct team id in the customer's metadata.
Release Notes
Documentation
Werft options: