@incodetech/prizma-core-screens 0.1.1 → 0.1.3

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.
@@ -31,7 +31,17 @@ export interface EmailInputStrings {
31
31
  verify: {
32
32
  /** H2 ("Verify your email"). */
33
33
  title: string;
34
- /** H5 ("We'll send you a code to ensure it's yours"). */
34
+ /**
35
+ * H5 ("We'll use it to verify it's yours").
36
+ *
37
+ * DELIBERATELY SILENT ABOUT THE CODE, for the same reason as Phone Input's
38
+ * twin line. This module ships in TWO configurations and the `Without a
39
+ * one-time code` one never asks for a code at all (see the `noOtp` variant
40
+ * in `flow/graphs/email-input.ts`: the spinner runs straight into the
41
+ * verdict). One screen serves both, and which configuration the session
42
+ * wants is not something this line can know. It answers "why do you want my
43
+ * address?" instead, which holds in both.
44
+ */
35
45
  subtitle: string;
36
46
  /** Field placeholder ("Email"). */
37
47
  placeholder: string;
@@ -45,7 +45,16 @@ export interface PhoneInputStrings {
45
45
  verify: {
46
46
  /** H2 ("Verify your phone number"). */
47
47
  title: string;
48
- /** H5 ("We'll send you a code to ensure it's yours"). */
48
+ /**
49
+ * H5 ("We'll use it to verify it's yours").
50
+ *
51
+ * DELIBERATELY SILENT ABOUT THE CODE. This screen is shared by both
52
+ * verification methods, and `Is number covered for SNA?` is decided AFTER
53
+ * the CTA (see `flow/graphs/phone-input.ts`) — so at the moment this line
54
+ * is read, nobody knows yet whether a code will be sent. It answers "why
55
+ * do you want my number?" instead, which is true on the silent leg, the
56
+ * OTP leg and the fallback alike.
57
+ */
49
58
  subtitle: string;
50
59
  /** Phone field placeholder ("(123) 123-45-67"). */
51
60
  placeholder: string;
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@incodetech/prizma-core-screens",
3
- "version": "0.1.1",
3
+ "version": "0.1.3",
4
4
  "description": "Prizma Design System — SDK module screens: composed, responsive, brand-themeable React screens built from @incodetech/prizma-core-web.",
5
5
  "license": "UNLICENSED",
6
6
  "type": "module",
@@ -678,8 +678,8 @@
678
678
  },
679
679
  "dependencies": {
680
680
  "@incodetech/prizma-core-icons": "^0.4.0",
681
- "@incodetech/prizma-core-tokens": "^0.10.3",
682
- "@incodetech/prizma-core-web": "^0.10.3"
681
+ "@incodetech/prizma-core-tokens": "^0.11.0",
682
+ "@incodetech/prizma-core-web": "^0.11.0"
683
683
  },
684
684
  "devDependencies": {
685
685
  "@types/react": "^18.3.12",
@@ -63,7 +63,17 @@ export interface EmailInputStrings {
63
63
  verify: {
64
64
  /** H2 ("Verify your email"). */
65
65
  title: string;
66
- /** H5 ("We'll send you a code to ensure it's yours"). */
66
+ /**
67
+ * H5 ("We'll use it to verify it's yours").
68
+ *
69
+ * DELIBERATELY SILENT ABOUT THE CODE, for the same reason as Phone Input's
70
+ * twin line. This module ships in TWO configurations and the `Without a
71
+ * one-time code` one never asks for a code at all (see the `noOtp` variant
72
+ * in `flow/graphs/email-input.ts`: the spinner runs straight into the
73
+ * verdict). One screen serves both, and which configuration the session
74
+ * wants is not something this line can know. It answers "why do you want my
75
+ * address?" instead, which holds in both.
76
+ */
67
77
  subtitle: string;
68
78
  /** Field placeholder ("Email"). */
69
79
  placeholder: string;
@@ -68,7 +68,16 @@ export interface PhoneInputStrings {
68
68
  verify: {
69
69
  /** H2 ("Verify your phone number"). */
70
70
  title: string;
71
- /** H5 ("We'll send you a code to ensure it's yours"). */
71
+ /**
72
+ * H5 ("We'll use it to verify it's yours").
73
+ *
74
+ * DELIBERATELY SILENT ABOUT THE CODE. This screen is shared by both
75
+ * verification methods, and `Is number covered for SNA?` is decided AFTER
76
+ * the CTA (see `flow/graphs/phone-input.ts`) — so at the moment this line
77
+ * is read, nobody knows yet whether a code will be sent. It answers "why
78
+ * do you want my number?" instead, which is true on the silent leg, the
79
+ * OTP leg and the fallback alike.
80
+ */
72
81
  subtitle: string;
73
82
  /** Phone field placeholder ("(123) 123-45-67"). */
74
83
  placeholder: string;