Tenancy context #30
Merged
Tenancy context #30
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ntext to the HttpContext so that it can be retrieved from it instead of relying on the AsyncLocal context
…nancyOptions class
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Added more features that makes it easier to use this package together with third party libraries and frameworks like Wolverine, Akka, etc.
Added
HttpContext.Itemdictionary and a way to easily retrieve it from theHttpContextwithout relying on theAsyncLocalTenantContextAccessorStaticTenantContextAccessorthat resolves either the statically configured tenant or the 'unresolved' tenant context. This type will be used instead of theAsyncLocalTenantContextAccessorifDisableAsyncLocalTenantContextmethod onTenancyBuilder. This can be useful if you're only interested in using the tenant context by passing it around in messages or using the one that's added to theHttpContext. For instance using frameworks and libraries that relies on running different processes on different threads or resuming contexts (Actor frameworks, Wolverine, etc.) then it can be useful to not rely on theAsyncLocalTenantContextAccessor