@incodetech/prizma-core-screens 0.1.2 → 0.1.3

package/dist/EmailInputStrings.d.ts

@@ -31,7 +31,17 @@ export interface EmailInputStrings {
     verify: {
         /** H2 ("Verify your email"). */
         title: string;
-        /** H5 ("We'll send you a code to ensure it's yours"). */
+        /**
+         * H5 ("We'll use it to verify it's yours").
+         *
+         * DELIBERATELY SILENT ABOUT THE CODE, for the same reason as Phone Input's
+         * twin line. This module ships in TWO configurations and the `Without a
+         * one-time code` one never asks for a code at all (see the `noOtp` variant
+         * in `flow/graphs/email-input.ts`: the spinner runs straight into the
+         * verdict). One screen serves both, and which configuration the session
+         * wants is not something this line can know. It answers "why do you want my
+         * address?" instead, which holds in both.
+         */
         subtitle: string;
         /** Field placeholder ("Email"). */
         placeholder: string;

package/dist/PhoneInputStrings.d.ts

@@ -45,7 +45,16 @@ export interface PhoneInputStrings {
     verify: {
         /** H2 ("Verify your phone number"). */
         title: string;
-        /** H5 ("We'll send you a code to ensure it's yours"). */
+        /**
+         * H5 ("We'll use it to verify it's yours").
+         *
+         * DELIBERATELY SILENT ABOUT THE CODE. This screen is shared by both
+         * verification methods, and `Is number covered for SNA?` is decided AFTER
+         * the CTA (see `flow/graphs/phone-input.ts`) — so at the moment this line
+         * is read, nobody knows yet whether a code will be sent. It answers "why
+         * do you want my number?" instead, which is true on the silent leg, the
+         * OTP leg and the fallback alike.
+         */
         subtitle: string;
         /** Phone field placeholder ("(123) 123-45-67"). */
         placeholder: string;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@incodetech/prizma-core-screens",
-  "version": "0.1.2",
+  "version": "0.1.3",
   "description": "Prizma Design System — SDK module screens: composed, responsive, brand-themeable React screens built from @incodetech/prizma-core-web.",
   "license": "UNLICENSED",
   "type": "module",

package/src/EmailInputStrings.ts

@@ -63,7 +63,17 @@ export interface EmailInputStrings {
   verify: {
     /** H2 ("Verify your email"). */
     title: string;
-    /** H5 ("We'll send you a code to ensure it's yours"). */
+    /**
+     * H5 ("We'll use it to verify it's yours").
+     *
+     * DELIBERATELY SILENT ABOUT THE CODE, for the same reason as Phone Input's
+     * twin line. This module ships in TWO configurations and the `Without a
+     * one-time code` one never asks for a code at all (see the `noOtp` variant
+     * in `flow/graphs/email-input.ts`: the spinner runs straight into the
+     * verdict). One screen serves both, and which configuration the session
+     * wants is not something this line can know. It answers "why do you want my
+     * address?" instead, which holds in both.
+     */
     subtitle: string;
     /** Field placeholder ("Email"). */
     placeholder: string;

package/src/PhoneInputStrings.ts

@@ -68,7 +68,16 @@ export interface PhoneInputStrings {
   verify: {
     /** H2 ("Verify your phone number"). */
     title: string;
-    /** H5 ("We'll send you a code to ensure it's yours"). */
+    /**
+     * H5 ("We'll use it to verify it's yours").
+     *
+     * DELIBERATELY SILENT ABOUT THE CODE. This screen is shared by both
+     * verification methods, and `Is number covered for SNA?` is decided AFTER
+     * the CTA (see `flow/graphs/phone-input.ts`) — so at the moment this line
+     * is read, nobody knows yet whether a code will be sent. It answers "why
+     * do you want my number?" instead, which is true on the silent leg, the
+     * OTP leg and the fallback alike.
+     */
     subtitle: string;
     /** Phone field placeholder ("(123) 123-45-67"). */
     placeholder: string;