@ciromaciel/auth-react 1.0.2 → 1.2.0

package/README.md

@@ -77,7 +77,10 @@ Or use the ready-made screen:
     authenticatedRedirect="/" // where to send someone who already has a session
     onCodeSent={email => notify(`Code sent to ${email}`)}
     onSuccess={(user, { result, redirectHandled }) => notify(`Welcome ${user?.email}`)}
-    onError={error => notify(error.message)} // error.code carries the stable identifier
+    onError={(error, { isShownOnCard }) => {
+        // A wrong, expired or exhausted code is already explained on the card
+        if (!isShownOnCard) notify(error.message) // error.code carries the stable identifier
+    }}
 />
 ```
 
@@ -87,6 +90,10 @@ Or use the ready-made screen:
   `redirectOrigins` adds domains and `handleRedirect={false}` hands control back to the app.
 - A wrong code fails with `error.details.attemptsLeft`. Five wrong tries destroy the request and
   the person asks for a new code.
+- On the code step the card explains every failure itself: how many tries are left, or, once the
+  code is exhausted or expired, a button that sends a new one. `onError` still fires, with a second
+  argument `{ step: 'request' | 'verify', isShownOnCard }`; skip your own notification when
+  `isShownOnCard` is `true`, or the person reads the same failure twice.
 
 ### Social sign-in
 
@@ -104,6 +111,29 @@ reads the token the callback leaves in the URL fragment — `AuthProvider` alrea
 for you. `startSocialLink()`, `unlinkSocialProvider()` and `getLinkedProviders()` manage the
 connections of an account that is already signed in.
 
+### Recent accounts
+
+`<SignIn />` remembers the accounts that signed in on this browser and, on the next visit, shows
+them before the email field. One click on an account sends the code (or goes back to the provider
+that account used last time) and opens the code step. With nothing saved, the screen is the plain
+email form.
+
+- An account is saved only after a session exists: the code confirmed, or the provider's token
+  back. A mistyped email never becomes a suggestion.
+- The list keeps the five most recent accounts. Each entry holds the email, the way in and the
+  time of the last sign-in. It lives in `localStorage` under `auth:recent-accounts`, so each
+  origin keeps its own list.
+- Signing out keeps the list. "Gerenciar" on the screen removes an account; nothing else about
+  that account changes.
+
+```jsx
+<SignIn />                         {/* shows and saves recent accounts */}
+<SignIn recentAccounts={false} />  {/* shared computers: neither shows nor saves */}
+```
+
+Building your own screen? `listRecentAccounts()`, `rememberAccount(email, method)` and
+`forgetAccount(email)` read and write the same list.
+
 ## API
 
 ### Components