MultiTenantContext can be null?
See original GitHub issueIt seems that if no tenant was resolved, MultiTenantContextAccessor<T>
will return null for MultiTenantContext
. So should this warrant a nullable reference?
Issue Analytics
- State:
- Created 2 years ago
- Comments:11 (5 by maintainers)
Top Results From Across the Web
NET Core Multi Tenant localhost is null after setting
MultiTenant should work with either approach--I'll try to clarify how it works below. It looks like you are setting the tenant info yourself, ......
Read more >value is always null when using HttpContext.User.Identity. ...
I am using .net core 6.0 I am struggling with this issue for past 2 days and could not resolve it. This value...
Read more >MultiTenant Strategies
Multiple strategies can be registered after AddMultiTenant<T> and each strategy will be tried in the order configured until a non-null identifier is returned....
Read more >Null and undefined (Reference) - Prisma
How Prisma Client handles null and undefined, including a GraphQL use case. ... return "ariadne@prisma.io"; // Could be null! } return null;.
Read more >Tenent coming as null during Springboot - Flowable forum
This means that you did not set any tenant on booting up. The exception means that some processes have been tried be deployed...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@Bouke I agree with you that both as nullable is annoying – I think for the next major release I’ll have
MultiTenantContext
be non-nullable. No set timeframe for that yet though.Ugh stale bot 👎.