docs(firebase_ui_auth): fix phone provider's widget example #10917
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.
Added handling for the auth state of SMSCodeRequested in the custom AuthFlowBuilder example, matching the implementation of the PhoneInputView.
Description
This PR includes only a small documentation edit for the phone auth provider in the firebase_ui_auth package.
The example for building a custom widget with AuthFlowBuilder, doesn't handle the auth state for SMSCodeRequested. When copy-pasting this example, it temporarily returns an unknown state text widget during login (see image below). I've fixed the example, modifying it based on the condition in the PhoneInputView widget.
Related Issues
None.
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes (
[x]
).This will ensure a smooth and quick review process. Updating the
pubspec.yaml
and changelogs is not required.///
).melos run analyze
) does not report any problems on my PR.Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?