We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ITenantInfo
Why does ITenantInfo have property setters?
To the best of my understanding, they are only used in tests.
ITenantInfo interface could be simplified to use only getters. And tests may use a TestTenantInfo with setters.
TestTenantInfo
While on this page, why Identifier and Name?
Identifier
Name
The absolutely minimum required is Id. And it should not be nullable.
Id
Other properties seem to be used only for some specific cases/strategies. It could be refactored.
Sadly, the 7.0 release has already shipped. Maybe in 8.0?
7.0
8.0
I can work on some PRs, if interested.
The text was updated successfully, but these errors were encountered:
Update:
Correction: The interface setters are not used anywhere. Tests always use TenantInfo class, which already does have setters.
TenantInfo
ITenantInfo interface can be simplified to use only getters.
I did a POC right now in a local fork and everything builds fine. I can provide my own custom ITenantInfo implementation without the need for setters.
Sorry, something went wrong.
Yes you are right. I would like to clean this up on the next major release and have ITenantInfo instances be treated more like an immutable.
No branches or pull requests
Why does
ITenantInfo
have property setters?To the best of my understanding, they are only used in tests.
ITenantInfo
interface could be simplified to use only getters. And tests may use aTestTenantInfo
with setters.While on this page, why
Identifier
andName
?The absolutely minimum required is
Id
. And it should not be nullable.Other properties seem to be used only for some specific cases/strategies. It could be refactored.
Sadly, the
7.0
release has already shipped. Maybe in8.0
?I can work on some PRs, if interested.
The text was updated successfully, but these errors were encountered: