[SDK-1911] Always use UsernamePane when using custom resolver #1918
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.
Changes
This PR causes Lock to show the username pane instead of the email pane when
connectionResolver
is specified. This is so that the validation for that field works as intended when the type of connection can be changed dynamically between those that require a username, and those that don't.References
Fixes #1732
Testing
Unit tests added to verify functionality of using
connectionResolver
to force username input.Checklist