feat: add ability to customize model and table name

[leek]

No description provided.

[chrisreedio]

I think everything but that one line looks good.

[leek]

I think everything but that one line looks good.

Fixed 👍

[leek]

@chrisreedio This is a super small PR that is fully backwards compatible. Can we get this one merged?

[chrisreedio]

If we're allowing customization of the Connected Account model, should we just depend on that model to set the table name?

Might make the migration kind of "weird" but would prevent any issues of setting the table name to one thing in the config and the model having a different one?

Still thinking about this a bit.

[leek]

If we're allowing customization of the Connected Account model, should we just depend on that model to set the table name?

Might make the migration kind of "weird" but would prevent any issues of setting the table name to one thing in the config and the model having a different one?

Still thinking about this a bit.

This PR allows you to override the model or just override the table name. This is how Spatie packages handle this (example).

I just want the table name to be plural to follow Laravel standards without having to use a fork.

/cc @chrisreedio

[chrisreedio]

If we're allowing customization of the Connected Account model, should we just depend on that model to set the table name?

Might make the migration kind of "weird" but would prevent any issues of setting the table name to one thing in the config and the model having a different one?

Still thinking about this a bit.

This PR allows you to override the model or just override the table name. This is how Spatie packages handle this.

I just want the table name to be plural to follow Laravel standards without having to use a fork.

/cc @chrisreedio

Before this PR the table name was already plural?

[leek]

Before this PR the table name was already plural?

Oh weird. I could have sworn it used to create connected_account. My mistake.