Foreign key configuration for `BelongsTo` or `HasMany` relationship.

[scaabel]

Foreign key configuration for `BelongsTo` or `HasMany` relationship.

[stancl]

I see, seems like the HasDomains trait should be using something like BelongsToTenant::$tenantIdColumn as well instead of the literal tenant_id string.

We changed this in v4 to use a config key instead of a trait property, since PHP 8.1 shows deprecation notices when you try to access trait properties (#854): 24146b2

But I see your point that this relates to HasDomains as well, and not just single-db Tenancy traits/columns.

The change you proposed to BelongsToTenant seems to be fully implemented here already (correct me if I'm wrong): 24146b2#diff-3f95188061d3fafb597105f47adbb923c98d5b4da9a9839c4a944627c5277981R17-R27

And for the HasDomains trait, you can currently just override the method, but I agree that we should add a config key.

[stancl]

Thanks for opening the issue!

[scaabel]

I see, seems like the HasDomains trait should be using something like BelongsToTenant::$tenantIdColumn as well instead of the literal tenant_id string.

We changed this in v4 to use a config key instead of a trait property, since PHP 8.1 shows deprecation notices when you try to access trait properties (#854): 24146b2

But I see your point that this relates to HasDomains as well, and not just single-db Tenancy traits/columns.

The change you proposed to BelongsToTenant seems to be fully implemented here already (correct me if I'm wrong): 24146b2#diff-3f95188061d3fafb597105f47adbb923c98d5b4da9a9839c4a944627c5277981R17-R27

And for the HasDomains trait, you can currently just override the method, but I agree that we should add a config key.

Thanks @stancl .