During a clean-up of this repository I (yes, me) accidentally introduces the propeties to the TenantDescriptor#equals method.
This was, as it turns out, wrong.
The TenantDescriptor is both constructed by the extension it self and by users, both not necessarily knowledgable about the properties, but definitely knowledgable about the right tenantId.
To have the multi-tenancy extension behave as intended, validating the TenantDescriptor based on just it's tenantId is paramount.
As such, this pull request removes properties from the TenantDescriptor#equals method again.
Furthermore, I have added a test case to validate the properties field does not have any influence on the behavior of equals.
During a clean-up of this repository I (yes, me) accidentally introduces the
propeties
to theTenantDescriptor#equals
method. This was, as it turns out, wrong.The
TenantDescriptor
is both constructed by the extension it self and by users, both not necessarily knowledgable about the properties, but definitely knowledgable about the righttenantId
. To have the multi-tenancy extension behave as intended, validating theTenantDescriptor
based on just it'stenantId
is paramount.As such, this pull request removes
properties
from theTenantDescriptor#equals
method again. Furthermore, I have added a test case to validate theproperties
field does not have any influence on the behavior ofequals
.