Support custom table names

[sasokovacic]

Table names should be configurable so we can prefix them or just use custom names

[driesvints]

No plans for this.

[sasokovacic]

@driesvints what a "great" response... no explanation, just shutdown. thanks ;)

[driesvints]

You can already overwrite the current migrations if you want: https://laravel.com/docs/8.x/billing#database-migrations

But changing the table names will conflict with the existing Eloquent models. That makes it hard to introduce custom table names. In general we don't want to support this because most use cases don't need custom table support and introducing this for a small minority just brings on an unnecessary maintenance burdon on us.

[sasokovacic]

What about a configurable Subscription model? You already support a custom billable model. If I can set my own Subscription model in the configuration, then I'm able to make a new Subscription model that extends yours and set a new table name directly in it. Then I just overwrite your migrations and I'm done.
Correct me if I'm wrong but the only thing on your part, in this case, is you have to add a new line in the config file and use it in the subscriptions method in the Billable trait. But maybe I'm wrong.

[driesvints]

Well actually, adding model swapping in the same fashion as Passport & Sanctum isn't a bad idea at all. I've just sent in a PR to do just that: #1067

[sasokovacic]

Great. That was fast. Thanks. Have a great day :)

[driesvints]

No worries. Sorry if I was a bit terse at first. Thanks for bringing this up 👍