Refactor the tenant child model functionality for sub-tenancies #107
Labels
status: accepted
The issue has been accepted/acknowledged and is being actioned or will be
status: investigating
The issue is being investigated
type: refactor
Refactoring of code
The Eloquent child model functionality will need looking at, as it currently relies on the tenancy name coming from a method, and restricts usage of TenantRelation to a single method. I believe the following is the best way to improve this to better support sub-tenancies:
The text was updated successfully, but these errors were encountered: