@beezping/adapter-prisma 0.7.0 → 0.8.0

package/dist/email.d.cts

@@ -1,5 +1,5 @@
 /**
- * The one email pattern every Siteping surface validates against.
+ * The one email pattern every Beezping surface validates against.
  *
  * The widget's identity modal and the HTTP handler's schema used to disagree
  * (a permissive regex on one side, an ASCII-only default on the other), so an
@@ -8,12 +8,15 @@
  * sides, makes that drift impossible.
  *
  * Deliberately Unicode-aware: internationalised local parts and domains
- * (`françois@exemple.fr`, `user@münchen.de`) are real addresses and common in
- * the audience this widget serves. Structure follows the usual rules — a
- * local part of 1 to 64 characters with no leading, trailing or doubled dot,
+ * (`françois@exemple.fr`, `user@münchen.de`, `user@हिंदी.भारत`) are real
+ * addresses and common in the audience this widget serves. Combining marks
+ * (`\p{M}`) are allowed alongside letters — scripts like Devanagari need them,
+ * and NFD-composed input spells `ç` as `c` + U+0327 — except as the first
+ * character of a domain label. Structure follows the usual rules — a local
+ * part of 1 to 64 characters with no leading, trailing or doubled dot,
  * dot-separated domain labels of at most 63 characters that neither start nor
  * end with a hyphen, and a final label of at least two characters.
  */
 export declare const EMAIL_PATTERN: RegExp;
-/** Whether `value` is an email address Siteping accepts — see {@link EMAIL_PATTERN}. */
+/** Whether `value` is an email address Beezping accepts — see {@link EMAIL_PATTERN}. */
 export declare function isValidEmail(value: string): boolean;

package/dist/email.d.ts

@@ -1,5 +1,5 @@
 /**
- * The one email pattern every Siteping surface validates against.
+ * The one email pattern every Beezping surface validates against.
  *
  * The widget's identity modal and the HTTP handler's schema used to disagree
  * (a permissive regex on one side, an ASCII-only default on the other), so an
@@ -8,12 +8,15 @@
  * sides, makes that drift impossible.
  *
  * Deliberately Unicode-aware: internationalised local parts and domains
- * (`françois@exemple.fr`, `user@münchen.de`) are real addresses and common in
- * the audience this widget serves. Structure follows the usual rules — a
- * local part of 1 to 64 characters with no leading, trailing or doubled dot,
+ * (`françois@exemple.fr`, `user@münchen.de`, `user@हिंदी.भारत`) are real
+ * addresses and common in the audience this widget serves. Combining marks
+ * (`\p{M}`) are allowed alongside letters — scripts like Devanagari need them,
+ * and NFD-composed input spells `ç` as `c` + U+0327 — except as the first
+ * character of a domain label. Structure follows the usual rules — a local
+ * part of 1 to 64 characters with no leading, trailing or doubled dot,
  * dot-separated domain labels of at most 63 characters that neither start nor
  * end with a hyphen, and a final label of at least two characters.
  */
 export declare const EMAIL_PATTERN: RegExp;
-/** Whether `value` is an email address Siteping accepts — see {@link EMAIL_PATTERN}. */
+/** Whether `value` is an email address Beezping accepts — see {@link EMAIL_PATTERN}. */
 export declare function isValidEmail(value: string): boolean;

package/dist/errors.d.cts

@@ -1,5 +1,5 @@
 /**
- * Typed error hierarchy for Siteping client/server boundaries.
+ * Typed error hierarchy for Beezping client/server boundaries.
  *
  * Consumers can `instanceof`-check or read `code` / `retryable` instead of
  * pattern-matching error messages. Designed to be additive on top of the
@@ -7,35 +7,49 @@
  * remain the canonical signals for server-side store implementations.
  *
  * Usage on the widget side (api-client.ts):
- *   - fetch failures / aborts / timeouts → `SitepingNetworkError` (retryable)
- *   - HTTP 4xx (except 401/403)         → `SitepingValidationError` (not retryable)
- *   - HTTP 401 / 403                    → `SitepingAuthError` (not retryable)
- *   - everything else                   → `SitepingError` generic
+ *   - fetch failures / aborts / timeouts → `BeezpingNetworkError` (retryable)
+ *   - HTTP 4xx (except 401/403)         → `BeezpingValidationError` (not retryable)
+ *   - HTTP 401 / 403                    → `BeezpingAuthError` (not retryable)
+ *   - everything else                   → `BeezpingError` generic
+ *
+ * Store mode (store-client.ts): a `createFeedback` that does not settle in
+ * time → `BeezpingError` with code `"TIMEOUT"` (retryable).
  *
  * `retryable` is meta information surfaced to host apps that want to wire
  * their own retry/queue/backoff strategy — the widget already retries
  * network failures via its built-in retry queue.
  */
 /**
- * Discriminant string carried by every `SitepingError`. Subclasses pin a
+ * Discriminant string carried by every `BeezpingError`. Subclasses pin a
  * literal value; the base class accepts a wider string so userland can
  * extend the hierarchy without colliding with built-ins.
  */
-export type SitepingErrorCode = "NETWORK" | "VALIDATION" | "AUTH" | "SERVER" | (string & {});
-export declare class SitepingError<TCode extends SitepingErrorCode = SitepingErrorCode> extends Error {
+export type BeezpingErrorCode = "NETWORK" | "VALIDATION" | "AUTH" | "SERVER" | "TIMEOUT" | (string & {});
+export declare class BeezpingError<TCode extends BeezpingErrorCode = BeezpingErrorCode> extends Error {
     readonly code: TCode;
     readonly retryable: boolean;
     constructor(message: string, code: TCode, retryable: boolean);
 }
 /** Network-level failure: connection refused, DNS, CORS, timeout, abort. Retryable. */
-export declare class SitepingNetworkError extends SitepingError<"NETWORK"> {
+export declare class BeezpingNetworkError extends BeezpingError<"NETWORK"> {
     constructor(message: string);
 }
-/** Server rejected the request (4xx, not auth). Validation problem on the client side. */
-export declare class SitepingValidationError extends SitepingError<"VALIDATION"> {
-    constructor(message: string);
+/**
+ * Server rejected the request (4xx, not auth). Validation problem on the
+ * client side. `status` is the HTTP status when a response said so: a 404
+ * (the target is gone) and a 409 (a full thread) call for other answers
+ * than a 400.
+ */
+export declare class BeezpingValidationError extends BeezpingError<"VALIDATION"> {
+    readonly status: number | undefined;
+    constructor(message: string, status?: number);
 }
 /** Server rejected auth (401 or 403). Not retryable without fresh credentials. */
-export declare class SitepingAuthError extends SitepingError<"AUTH"> {
-    constructor(message: string);
+export declare class BeezpingAuthError extends BeezpingError<"AUTH"> {
+    /**
+     * `401`: the credentials are missing or no longer work — drop a dead token
+     * on this one. `403`: they work, and the server's policy refuses this request.
+     */
+    readonly status: 401 | 403;
+    constructor(message: string, status: 401 | 403);
 }

package/dist/errors.d.ts

@@ -1,5 +1,5 @@
 /**
- * Typed error hierarchy for Siteping client/server boundaries.
+ * Typed error hierarchy for Beezping client/server boundaries.
  *
  * Consumers can `instanceof`-check or read `code` / `retryable` instead of
  * pattern-matching error messages. Designed to be additive on top of the
@@ -7,35 +7,49 @@
  * remain the canonical signals for server-side store implementations.
  *
  * Usage on the widget side (api-client.ts):
- *   - fetch failures / aborts / timeouts → `SitepingNetworkError` (retryable)
- *   - HTTP 4xx (except 401/403)         → `SitepingValidationError` (not retryable)
- *   - HTTP 401 / 403                    → `SitepingAuthError` (not retryable)
- *   - everything else                   → `SitepingError` generic
+ *   - fetch failures / aborts / timeouts → `BeezpingNetworkError` (retryable)
+ *   - HTTP 4xx (except 401/403)         → `BeezpingValidationError` (not retryable)
+ *   - HTTP 401 / 403                    → `BeezpingAuthError` (not retryable)
+ *   - everything else                   → `BeezpingError` generic
+ *
+ * Store mode (store-client.ts): a `createFeedback` that does not settle in
+ * time → `BeezpingError` with code `"TIMEOUT"` (retryable).
  *
  * `retryable` is meta information surfaced to host apps that want to wire
  * their own retry/queue/backoff strategy — the widget already retries
  * network failures via its built-in retry queue.
  */
 /**
- * Discriminant string carried by every `SitepingError`. Subclasses pin a
+ * Discriminant string carried by every `BeezpingError`. Subclasses pin a
  * literal value; the base class accepts a wider string so userland can
  * extend the hierarchy without colliding with built-ins.
  */
-export type SitepingErrorCode = "NETWORK" | "VALIDATION" | "AUTH" | "SERVER" | (string & {});
-export declare class SitepingError<TCode extends SitepingErrorCode = SitepingErrorCode> extends Error {
+export type BeezpingErrorCode = "NETWORK" | "VALIDATION" | "AUTH" | "SERVER" | "TIMEOUT" | (string & {});
+export declare class BeezpingError<TCode extends BeezpingErrorCode = BeezpingErrorCode> extends Error {
     readonly code: TCode;
     readonly retryable: boolean;
     constructor(message: string, code: TCode, retryable: boolean);
 }
 /** Network-level failure: connection refused, DNS, CORS, timeout, abort. Retryable. */
-export declare class SitepingNetworkError extends SitepingError<"NETWORK"> {
+export declare class BeezpingNetworkError extends BeezpingError<"NETWORK"> {
     constructor(message: string);
 }
-/** Server rejected the request (4xx, not auth). Validation problem on the client side. */
-export declare class SitepingValidationError extends SitepingError<"VALIDATION"> {
-    constructor(message: string);
+/**
+ * Server rejected the request (4xx, not auth). Validation problem on the
+ * client side. `status` is the HTTP status when a response said so: a 404
+ * (the target is gone) and a 409 (a full thread) call for other answers
+ * than a 400.
+ */
+export declare class BeezpingValidationError extends BeezpingError<"VALIDATION"> {
+    readonly status: number | undefined;
+    constructor(message: string, status?: number);
 }
 /** Server rejected auth (401 or 403). Not retryable without fresh credentials. */
-export declare class SitepingAuthError extends SitepingError<"AUTH"> {
-    constructor(message: string);
+export declare class BeezpingAuthError extends BeezpingError<"AUTH"> {
+    /**
+     * `401`: the credentials are missing or no longer work — drop a dead token
+     * on this one. `403`: they work, and the server's policy refuses this request.
+     */
+    readonly status: 401 | 403;
+    constructor(message: string, status: 401 | 403);
 }

package/dist/filters.d.cts

@@ -4,13 +4,14 @@
  * near-identical copies of the same logic. Any adapter that holds an
  * in-memory snapshot of feedbacks can use it.
  *
- * Filtering order matches the historical adapter behaviour:
- *   1. projectName  (always required)
- *   2. type
- *   3. status / statuses  (`statuses` bucket wins when both are set)
- *   4. url
- *   5. urlPattern
- *   6. search       (lowercase substring match on `message`)
+ * A record matches when it passes every active filter (see
+ * {@link matchesFeedbackQuery}):
+ *   - projectName  (always required)
+ *   - type
+ *   - status / statuses  (`statuses` bucket wins when both are set)
+ *   - url
+ *   - urlPattern
+ *   - search       (lowercase substring match on `message`)
  *
  * Pagination goes through `clampPagination`: `limit` capped at 100, `page`
  * 1-based, both clamped up to 1 rather than indexing backwards from the end
@@ -63,6 +64,13 @@ export declare function clampPagination(query: Pick<FeedbackQuery, "page" | "lim
  * @returns `true` when no row can sit at that offset.
  */
 export declare function isUnreachableOffset(skip: number): boolean;
+/**
+ * Whether one record passes every filter of `query` — the filter half of
+ * {@link applyFeedbackFilters}, exposed so a client holding a single record
+ * (e.g. the dashboard deciding whether an optimistic edit still belongs in
+ * its list) applies exactly the stores' semantics. Pagination is ignored.
+ */
+export declare function matchesFeedbackQuery(record: FeedbackRecord, query: FeedbackQuery): boolean;
 /**
  * Apply the standard feedback filter + pagination pipeline against an
  * in-memory snapshot. Used by `MemoryStore.getFeedbacks` and

package/dist/filters.d.ts

@@ -4,13 +4,14 @@
  * near-identical copies of the same logic. Any adapter that holds an
  * in-memory snapshot of feedbacks can use it.
  *
- * Filtering order matches the historical adapter behaviour:
- *   1. projectName  (always required)
- *   2. type
- *   3. status / statuses  (`statuses` bucket wins when both are set)
- *   4. url
- *   5. urlPattern
- *   6. search       (lowercase substring match on `message`)
+ * A record matches when it passes every active filter (see
+ * {@link matchesFeedbackQuery}):
+ *   - projectName  (always required)
+ *   - type
+ *   - status / statuses  (`statuses` bucket wins when both are set)
+ *   - url
+ *   - urlPattern
+ *   - search       (lowercase substring match on `message`)
  *
  * Pagination goes through `clampPagination`: `limit` capped at 100, `page`
  * 1-based, both clamped up to 1 rather than indexing backwards from the end
@@ -63,6 +64,13 @@ export declare function clampPagination(query: Pick<FeedbackQuery, "page" | "lim
  * @returns `true` when no row can sit at that offset.
  */
 export declare function isUnreachableOffset(skip: number): boolean;
+/**
+ * Whether one record passes every filter of `query` — the filter half of
+ * {@link applyFeedbackFilters}, exposed so a client holding a single record
+ * (e.g. the dashboard deciding whether an optimistic edit still belongs in
+ * its list) applies exactly the stores' semantics. Pagination is ignored.
+ */
+export declare function matchesFeedbackQuery(record: FeedbackRecord, query: FeedbackQuery): boolean;
 /**
  * Apply the standard feedback filter + pagination pipeline against an
  * in-memory snapshot. Used by `MemoryStore.getFeedbacks` and

package/dist/i18n.d.cts

@@ -48,6 +48,24 @@ export interface I18n<T> {
      */
     registerLocale(code: string, translations: Partial<T>): void;
 }
+/**
+ * `locale` as `Intl` accepts it. Locale options take any string, and a
+ * backend-style tag (`fr_FR` from PHP / WordPress) makes every `Intl`
+ * constructor and `toLocale*` call throw a RangeError: `_` reads as `-`, and
+ * a tag `Intl` still rejects falls back to English, as `createT` does.
+ * Silent, so it is safe on a render path; see `canonicalizeLocale` for the
+ * one-time, warning variant.
+ */
+export declare function intlLocale(locale: string): string;
+/**
+ * The host's locale tag as `Intl` accepts it. `BeezpingLocale` takes any
+ * string, and PHP / WordPress hand out POSIX-style tags (`fr_FR`, `pt_BR`)
+ * that every `Intl` constructor rejects with a RangeError: `_` becomes `-`,
+ * then the tag is canonicalised (`fr-FR`). Falls back to `"en"`, with a
+ * warning, only when the tag is still invalid (empty, garbage) — meant to run
+ * once, where the config is read.
+ */
+export declare function canonicalizeLocale(locale: string): string;
 /**
  * Build the i18n machinery for one message catalog.
  *

package/dist/i18n.d.ts

@@ -48,6 +48,24 @@ export interface I18n<T> {
      */
     registerLocale(code: string, translations: Partial<T>): void;
 }
+/**
+ * `locale` as `Intl` accepts it. Locale options take any string, and a
+ * backend-style tag (`fr_FR` from PHP / WordPress) makes every `Intl`
+ * constructor and `toLocale*` call throw a RangeError: `_` reads as `-`, and
+ * a tag `Intl` still rejects falls back to English, as `createT` does.
+ * Silent, so it is safe on a render path; see `canonicalizeLocale` for the
+ * one-time, warning variant.
+ */
+export declare function intlLocale(locale: string): string;
+/**
+ * The host's locale tag as `Intl` accepts it. `BeezpingLocale` takes any
+ * string, and PHP / WordPress hand out POSIX-style tags (`fr_FR`, `pt_BR`)
+ * that every `Intl` constructor rejects with a RangeError: `_` becomes `-`,
+ * then the tag is canonicalised (`fr-FR`). Falls back to `"en"`, with a
+ * warning, only when the tag is still invalid (empty, garbage) — meant to run
+ * once, where the config is read.
+ */
+export declare function canonicalizeLocale(locale: string): string;
 /**
  * Build the i18n machinery for one message catalog.
  *