Add Passwordless.AspNetCore
registration overloads that support IConfiguration
properly
#146
+239
−112
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.
This PR fixes an issue where, when registering the Passwordless Identity integration, the core options (
PasswordlessOptions
) were not initialized with reload-tracking, due to the fact that the SDK was registered withservices.AddPasswordlessSdk(_ => {})
. Even though we forwarded the options by re-registering them inside the Identity integration, this did not forward the corresponding reload token.I also added a few tests for configuration-related scenarios, although properly e2e testing configuration routing is quite challenging.