Howdy, is there any smart reason, why

SolidusSubscriptions::Subscription

does not have

dependent: destroy

on some of its child models, like

Installment

or

InstallmentDetail

? I figure maybe just an oversight but perhaps someone has a smart reason for this.

I'm not aware of any, most likely an oversight 👍

Ok get ready for a PR!

Not sure how smart this is but I believe they decided that it didn't make sense to have dependent: destroy on the child models because the data in those models is needed for the parent model. If you delete the child models, then the parent model won't have the data it needs.

I haven’t done this for awhile so forgive my innocence but I thought this will allow cascading `destroy`s? So If a subscription is destroyed, so will the installment, events, and installment details?

If the child models are destroyed, then the parent model won't have the data it needs. For example, if the installments are destroyed, then the subscription won't know how much it owes.

Yeah I get that.

I see what you're saying. You plan on adding the dependent:destroy to the child models.

Yes my bad!

Also if you delete a subscription by mistake that may be an issue.