@authowl/react 0.17.1 → 0.18.1

package/dist/index.d.cts

@@ -432,10 +432,13 @@ type MFARequiredGateProps = {
  * gate only wraps protected content, they re-sign-in into another pending
  * session without ever seeing enrolment.
  *
- * Before showing enrolment it CONFIRMS with an uncached session read: the
- * cookie-cached pending flag can be stale-true for up to 5 minutes after
- * another device completed enrolment, and re-running enrolment would
- * regenerate the user's TOTP secret.
+ * NOT REQUIRED for a client-rendered <SignIn/>: that component now finishes
+ * enrolment in place, so a project can turn required MFA on without every app
+ * having to adopt this gate first. The gate still matters for server-redirect
+ * layouts and for apps that reach protected content by another route.
+ *
+ * The stale-flag confirmation both surfaces depend on lives in
+ * `useConfirmedMfaPending`.
  */
 declare function MFARequiredGate({ children, title }: MFARequiredGateProps): React.JSX.Element | null;
 

package/dist/index.d.ts

@@ -432,10 +432,13 @@ type MFARequiredGateProps = {
  * gate only wraps protected content, they re-sign-in into another pending
  * session without ever seeing enrolment.
  *
- * Before showing enrolment it CONFIRMS with an uncached session read: the
- * cookie-cached pending flag can be stale-true for up to 5 minutes after
- * another device completed enrolment, and re-running enrolment would
- * regenerate the user's TOTP secret.
+ * NOT REQUIRED for a client-rendered <SignIn/>: that component now finishes
+ * enrolment in place, so a project can turn required MFA on without every app
+ * having to adopt this gate first. The gate still matters for server-redirect
+ * layouts and for apps that reach protected content by another route.
+ *
+ * The stale-flag confirmation both surfaces depend on lives in
+ * `useConfirmedMfaPending`.
  */
 declare function MFARequiredGate({ children, title }: MFARequiredGateProps): React.JSX.Element | null;