@authowl/react 0.18.0 → 0.18.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/index.d.cts CHANGED
@@ -311,12 +311,9 @@ type SignInPlan = {
311
311
  * passkeys inline. One place owns the token string.
312
312
  */
313
313
  declare function emailAutocomplete(isPasskeyHost: boolean): string;
314
- /**
315
- * Resolve the sign-in surfaces from a project's public config. On a config error
316
- * (`config` null) fall back to password - the safe default that always renders -
317
- * rather than showing nothing.
318
- */
319
- declare function resolveSignInMethods(config: PublicConfig | null): SignInPlan;
314
+ declare function resolveSignInMethods(config: PublicConfig | null,
315
+ /** The hostname the form is rendering on; omit when it is not knowable. */
316
+ pageHost?: string): SignInPlan;
320
317
 
321
318
  type SignInProps = {
322
319
  redirectTo?: string;
@@ -432,10 +429,13 @@ type MFARequiredGateProps = {
432
429
  * gate only wraps protected content, they re-sign-in into another pending
433
430
  * session without ever seeing enrolment.
434
431
  *
435
- * Before showing enrolment it CONFIRMS with an uncached session read: the
436
- * cookie-cached pending flag can be stale-true for up to 5 minutes after
437
- * another device completed enrolment, and re-running enrolment would
438
- * regenerate the user's TOTP secret.
432
+ * NOT REQUIRED for a client-rendered <SignIn/>: that component now finishes
433
+ * enrolment in place, so a project can turn required MFA on without every app
434
+ * having to adopt this gate first. The gate still matters for server-redirect
435
+ * layouts and for apps that reach protected content by another route.
436
+ *
437
+ * The stale-flag confirmation both surfaces depend on lives in
438
+ * `useConfirmedMfaPending`.
439
439
  */
440
440
  declare function MFARequiredGate({ children, title }: MFARequiredGateProps): React.JSX.Element | null;
441
441
 
package/dist/index.d.ts CHANGED
@@ -311,12 +311,9 @@ type SignInPlan = {
311
311
  * passkeys inline. One place owns the token string.
312
312
  */
313
313
  declare function emailAutocomplete(isPasskeyHost: boolean): string;
314
- /**
315
- * Resolve the sign-in surfaces from a project's public config. On a config error
316
- * (`config` null) fall back to password - the safe default that always renders -
317
- * rather than showing nothing.
318
- */
319
- declare function resolveSignInMethods(config: PublicConfig | null): SignInPlan;
314
+ declare function resolveSignInMethods(config: PublicConfig | null,
315
+ /** The hostname the form is rendering on; omit when it is not knowable. */
316
+ pageHost?: string): SignInPlan;
320
317
 
321
318
  type SignInProps = {
322
319
  redirectTo?: string;
@@ -432,10 +429,13 @@ type MFARequiredGateProps = {
432
429
  * gate only wraps protected content, they re-sign-in into another pending
433
430
  * session without ever seeing enrolment.
434
431
  *
435
- * Before showing enrolment it CONFIRMS with an uncached session read: the
436
- * cookie-cached pending flag can be stale-true for up to 5 minutes after
437
- * another device completed enrolment, and re-running enrolment would
438
- * regenerate the user's TOTP secret.
432
+ * NOT REQUIRED for a client-rendered <SignIn/>: that component now finishes
433
+ * enrolment in place, so a project can turn required MFA on without every app
434
+ * having to adopt this gate first. The gate still matters for server-redirect
435
+ * layouts and for apps that reach protected content by another route.
436
+ *
437
+ * The stale-flag confirmation both surfaces depend on lives in
438
+ * `useConfirmedMfaPending`.
439
439
  */
440
440
  declare function MFARequiredGate({ children, title }: MFARequiredGateProps): React.JSX.Element | null;
441
441