Skip to content

Commit 393f9cf

Browse files
docs: format
1 parent 71654b3 commit 393f9cf

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

FirebaseSwiftUI/README.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -578,7 +578,7 @@ struct ContentView: View {
578578
Button("Sign in with Google") {
579579
Task {
580580
do {
581-
let provider = GoogleProviderSwift( clientID: Auth.auth().app?.options.clientID ?? "")
581+
let provider = GoogleProviderSwift(clientID: Auth.auth().app?.options.clientID ?? "")
582582
let outcome = try await authService.signIn(provider)
583583

584584
// Handle MFA if required
@@ -767,7 +767,7 @@ Creates a new `AuthService` instance.
767767
##### Email Authentication
768768

769769
```swift
770-
public func withEmailSignIn(_ provider: EmailProviderSwift? = nil, onTap: @escaping () -> Void) -> AuthService
770+
public func withEmailSignIn(_ provider: EmailProviderSwift? = nil, onTap: @escaping () -> Void = {}) -> AuthService
771771
```
772772

773773
Enables email authentication and will render email sign-in directly within the AuthPickerView (default Views), email link sign-in is rendered as a button. When calling `AuthService.renderButtons()`, email link sign-in button is rendered. `onTap` custom callback (i.e where to navigate when tapped) allows user to control what happens when tapped. Default behavior in AuthPickerView is to push the user to email link sign-in default View.
@@ -785,7 +785,7 @@ authService
785785
// or
786786

787787
authService
788-
.withEmailSignIn(){
788+
.withEmailSignIn() {
789789
// navigate to email sign-in screen logic
790790
}
791791
```
@@ -795,7 +795,7 @@ authService
795795
##### Phone Authentication
796796

797797
```swift
798-
public func withPhoneSignIn(onTap: @escaping () -> Void) -> AuthService
798+
public func withPhoneSignIn(onTap: @escaping () -> Void = {}) -> AuthService
799799
```
800800

801801
Enables phone number authentication with SMS verification and will register a phone button that is rendered in AuthPickerView (default Views) or can be rendered in custom Views by calling `AuthService.renderButtons()`. `onTap` custom callback (i.e where to navigate when tapped) allows user to control what happens when tapped. Default behavior in AuthPickerView is to push the user to phone sign-in default View.

0 commit comments

Comments
 (0)