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.
Purpose
Easily supporting Stripe Subscriptions in your user facing applications shouldn't feel like a headache waiting to happen or a nightmare you're putting off. As part of the Starbase plugin ecosystem we want to tackle some of the hardest developer challenges with simple lines of required code so developers can focus on what makes their applications... theirs.
This pull request introduces the ability to provide two values from Stripe for your database to start tracking subscriptions. When the plugin is registered it will automatically create a SQL table on your behalf with the correct schema. When a user checks out a product via a Stripe Product Link the entries will be stored in your database automatically. And when a product/subscription is cancelled a webhook will be triggered that marks it with a soft delete by populating the
deleted_at
column in the database table.Tasks
Verify
Include the plugin in
./src/index.ts
Before
After
StripeDemo.mov