Update nullable annotations to correct handling of tenant ID #39
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.
Two scenarios had incorrect nullable annotations:
TryIdentifyTenant), if the tenant was not successfully identified, the output tenant ID should be allowed to be null.ConfigureTenantshould allow anulltenant ID to indicate the "default tenant."As part of this I enabled nullable annotations on the unit test projects to ensure things were lining up and allow us to see the nullable warnings when violations in test fixtures occur.
Includes a semver update from 8.0.1 => 8.0.2 for this fix. (My commit message has a typo. 😦 )