Use IdentityUserClaim<T>.ToClaim() to prevent data not being returned from table #102
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.
Use the
IdentityUserClaim<T>.ToClaim()
method to createClaim
instances from claim entities so that overridden behaviours are observed.Otherwise if a user creates a custom claim type, for example so they can store the claim issuer and claim value type, this information is lost when reading from the store as the additional data is not copied to the
Claim
instances created by the user store as only the Type and Value are used.An example of such a type is below.
After this change, additional properties added to the claim entity are correctly materialised from the table.
The behaviour for the out-of-the-box implementation is unchanged as the default
ToClaim()
implementation does the same as the store code did before the change.