Allow configuring names for the stripe_id
column on Cashier models.
#1656
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.
This PR allows for using a column other than
stripe_id
on the various Cashier models.It replaces all uses of
->stripe_id
with->stripeId()
which can be found in the new HasStripeId trait. This trait is included alongside the other traits in theBillable
trait, and in theSubscription
andSubscriptionItem
models.To make use of it, you would simply override the model's
public static $stripeIdColumn
property with whatever column name your model uses (including customSubscription
andSubscriptionItem
models that extend their Cashier counterparts).The purpose of this PR was so that in a project of mine I could use my custom models that mirror their actual Stripe counterparts 1:1 in my database. This allows me to both match the Stripe object schema and also more closely follow the Laravel/Eloquent schema pattern (in this case using
id
instead ofstripe_id
for theUser
[Customer
],Subscription
, andSubscriptionItem
models).