@fingerly/types 0.1.1 → 0.1.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
@@ -109,11 +109,6 @@ interface Lie {
109
109
  interface EngineIdentity {
110
110
  claimed?: string;
111
111
  observed?: string;
112
- /**
113
- * @deprecated Not sent since 0.1.1. The server compares [[claimed]] and
114
- * [[observed]] itself; kept so a report stored by an older SDK still types.
115
- */
116
- agrees?: boolean;
117
112
  }
118
113
  /** The tamper layer's findings. Raw; the server decides what they are worth. */
119
114
  interface IntegrityReport {
@@ -164,13 +159,8 @@ interface NativeIdentifyResult {
164
159
  * `null` when the server did not say.
165
160
  */
166
161
  duplicate: boolean | null;
162
+ /** As [[IdentifyResult.state]]. */
167
163
  state: string;
168
- /**
169
- * @deprecated An app is no longer told why a submission went unscored, so
170
- * this is `undefined`. Read `reason` on the server-side event read. See
171
- * [[IdentifyResult.reason]].
172
- */
173
- reason?: string;
174
164
  /** `null` when absent: unscored, or hidden by the SDK key. Not the same as zero. */
175
165
  suspectScore: number | null;
176
166
  /** `null` when absent, for the same reasons as [[suspectScore]]. */
@@ -274,18 +264,16 @@ interface IdentifyResult {
274
264
  * could be identified", which is the opposite of what happened.
275
265
  */
276
266
  duplicate: boolean;
277
- /** `enriched`, or `unavailable` when the address could not be looked up. */
278
- state: string;
279
267
  /**
280
- * @deprecated Browsers no longer receive this, so it is `undefined`.
268
+ * `enriched`, or `unavailable` when the address could not be looked up.
281
269
  *
282
270
  * Why an `unavailable` submission went unscored describes the service's own
283
- * infrastructure, which is nothing a visitor's page should be able to read.
284
- * Your backend reads it as `reason` on the server-side event read (`GET
285
- * /api/v1/events/{request_id}` with a secret key), by [[requestId]]. Kept,
286
- * optional, so code written against 0.1.0 still compiles.
271
+ * infrastructure, which is nothing a visitor's page should be able to read,
272
+ * so it is not on this result. Your backend reads it as `reason` on the
273
+ * server-side event read (`GET /api/v1/events/{request_id}` with a secret
274
+ * key), by [[requestId]].
287
275
  */
288
- reason?: string;
276
+ state: string;
289
277
  /**
290
278
  * The weighted sum of the signals that fired, under the weights in force when
291
279
  * this submission was scored.
package/dist/index.d.ts CHANGED
@@ -109,11 +109,6 @@ interface Lie {
109
109
  interface EngineIdentity {
110
110
  claimed?: string;
111
111
  observed?: string;
112
- /**
113
- * @deprecated Not sent since 0.1.1. The server compares [[claimed]] and
114
- * [[observed]] itself; kept so a report stored by an older SDK still types.
115
- */
116
- agrees?: boolean;
117
112
  }
118
113
  /** The tamper layer's findings. Raw; the server decides what they are worth. */
119
114
  interface IntegrityReport {
@@ -164,13 +159,8 @@ interface NativeIdentifyResult {
164
159
  * `null` when the server did not say.
165
160
  */
166
161
  duplicate: boolean | null;
162
+ /** As [[IdentifyResult.state]]. */
167
163
  state: string;
168
- /**
169
- * @deprecated An app is no longer told why a submission went unscored, so
170
- * this is `undefined`. Read `reason` on the server-side event read. See
171
- * [[IdentifyResult.reason]].
172
- */
173
- reason?: string;
174
164
  /** `null` when absent: unscored, or hidden by the SDK key. Not the same as zero. */
175
165
  suspectScore: number | null;
176
166
  /** `null` when absent, for the same reasons as [[suspectScore]]. */
@@ -274,18 +264,16 @@ interface IdentifyResult {
274
264
  * could be identified", which is the opposite of what happened.
275
265
  */
276
266
  duplicate: boolean;
277
- /** `enriched`, or `unavailable` when the address could not be looked up. */
278
- state: string;
279
267
  /**
280
- * @deprecated Browsers no longer receive this, so it is `undefined`.
268
+ * `enriched`, or `unavailable` when the address could not be looked up.
281
269
  *
282
270
  * Why an `unavailable` submission went unscored describes the service's own
283
- * infrastructure, which is nothing a visitor's page should be able to read.
284
- * Your backend reads it as `reason` on the server-side event read (`GET
285
- * /api/v1/events/{request_id}` with a secret key), by [[requestId]]. Kept,
286
- * optional, so code written against 0.1.0 still compiles.
271
+ * infrastructure, which is nothing a visitor's page should be able to read,
272
+ * so it is not on this result. Your backend reads it as `reason` on the
273
+ * server-side event read (`GET /api/v1/events/{request_id}` with a secret
274
+ * key), by [[requestId]].
287
275
  */
288
- reason?: string;
276
+ state: string;
289
277
  /**
290
278
  * The weighted sum of the signals that fired, under the weights in force when
291
279
  * this submission was scored.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@fingerly/types",
3
- "version": "0.1.1",
3
+ "version": "0.1.2",
4
4
  "publishConfig": {
5
5
  "access": "public"
6
6
  },