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.
Feedback collected when OpenIddict 1.x/2.x were released indicated that having multiple
OpenIddictApplication
/OpenIddictAuthorization
/OpenIddictScope
/OpenIddictToken
types in different assemblies (one set per stores) was a bit confusing. In 3.0, the entities, the stores and their resolvers will all be given a more specific name, likeOpenIddictMongoDbApplication
,OpenIddictMongoDbApplicationStore
andOpenIddictMongoDbApplicationStoreResolver
.This change should be transparent and initial tests show it shouldn't cause any issues with EF migrations.