@siteping/widget 0.10.7 → 0.10.8

package/dist/email.d.cts

@@ -0,0 +1,19 @@
+/**
+ * The one email pattern every Siteping 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
+ * address the modal accepted — and persisted in localStorage for good — came
+ * back as a 400 on every submission afterwards. One pattern, imported on both
+ * 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,
+ * 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}. */
+export declare function isValidEmail(value: string): boolean;

package/dist/email.d.ts

@@ -0,0 +1,19 @@
+/**
+ * The one email pattern every Siteping 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
+ * address the modal accepted — and persisted in localStorage for good — came
+ * back as a 400 on every submission afterwards. One pattern, imported on both
+ * 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,
+ * 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}. */
+export declare function isValidEmail(value: string): boolean;

package/dist/filters.d.cts

@@ -12,16 +12,41 @@
  *   5. urlPattern
  *   6. search       (lowercase substring match on `message`)
  *
- * Pagination clamps `limit` to a maximum of 100 and treats `page` as 1-based,
- * matching the public API contract documented on `getFeedbacks`. A page or
- * limit below 1 is clamped up to 1 rather than indexing backwards from the
- * end of the match set.
+ * Pagination goes through `clampPagination`: `limit` capped at 100, `page`
+ * 1-based, both clamped up to 1 rather than indexing backwards from the end
+ * of the match set. Query adapters reuse the same helper so every store
+ * paginates identically.
  */
 import type { FeedbackQuery, FeedbackRecord } from "./types.cjs";
+/** Default page size when the caller omits `query.limit`. */
+export declare const DEFAULT_PAGE_LIMIT = 50;
+/** Maximum allowed page size — defends against memory blow-ups on hostile callers. */
+export declare const MAX_PAGE_LIMIT = 100;
 export interface FilterResult {
     feedbacks: FeedbackRecord[];
     total: number;
 }
+/** Normalised pagination window — see {@link clampPagination}. */
+export interface Pagination {
+    /** 1-based page number, at least 1. */
+    page: number;
+    /** Page size in `[1, MAX_PAGE_LIMIT]`. */
+    limit: number;
+    /** Offset of the first row: `(page - 1) * limit`. */
+    skip: number;
+}
+/**
+ * Normalise `page` / `limit` to the store contract: `page` is 1-based and
+ * clamped up to 1, `limit` defaults to 50 and is clamped into `[1, 100]`,
+ * non-finite values fall back to the defaults. `skip` is the derived row
+ * offset for query backends (`OFFSET`, Prisma `skip`).
+ *
+ * Shared by the in-memory pipeline and query adapters (`PrismaStore`) so
+ * every store paginates identically — the HTTP schema clamps the same way,
+ * but direct callers (dashboard store mode, server actions) reach the store
+ * without a schema in front of them.
+ */
+export declare function clampPagination(query: Pick<FeedbackQuery, "page" | "limit">): Pagination;
 /**
  * Apply the standard feedback filter + pagination pipeline against an
  * in-memory snapshot. Used by `MemoryStore.getFeedbacks` and

package/dist/filters.d.ts

@@ -12,16 +12,41 @@
  *   5. urlPattern
  *   6. search       (lowercase substring match on `message`)
  *
- * Pagination clamps `limit` to a maximum of 100 and treats `page` as 1-based,
- * matching the public API contract documented on `getFeedbacks`. A page or
- * limit below 1 is clamped up to 1 rather than indexing backwards from the
- * end of the match set.
+ * Pagination goes through `clampPagination`: `limit` capped at 100, `page`
+ * 1-based, both clamped up to 1 rather than indexing backwards from the end
+ * of the match set. Query adapters reuse the same helper so every store
+ * paginates identically.
  */
 import type { FeedbackQuery, FeedbackRecord } from "./types.js";
+/** Default page size when the caller omits `query.limit`. */
+export declare const DEFAULT_PAGE_LIMIT = 50;
+/** Maximum allowed page size — defends against memory blow-ups on hostile callers. */
+export declare const MAX_PAGE_LIMIT = 100;
 export interface FilterResult {
     feedbacks: FeedbackRecord[];
     total: number;
 }
+/** Normalised pagination window — see {@link clampPagination}. */
+export interface Pagination {
+    /** 1-based page number, at least 1. */
+    page: number;
+    /** Page size in `[1, MAX_PAGE_LIMIT]`. */
+    limit: number;
+    /** Offset of the first row: `(page - 1) * limit`. */
+    skip: number;
+}
+/**
+ * Normalise `page` / `limit` to the store contract: `page` is 1-based and
+ * clamped up to 1, `limit` defaults to 50 and is clamped into `[1, 100]`,
+ * non-finite values fall back to the defaults. `skip` is the derived row
+ * offset for query backends (`OFFSET`, Prisma `skip`).
+ *
+ * Shared by the in-memory pipeline and query adapters (`PrismaStore`) so
+ * every store paginates identically — the HTTP schema clamps the same way,
+ * but direct callers (dashboard store mode, server actions) reach the store
+ * without a schema in front of them.
+ */
+export declare function clampPagination(query: Pick<FeedbackQuery, "page" | "limit">): Pagination;
 /**
  * Apply the standard feedback filter + pagination pipeline against an
  * in-memory snapshot. Used by `MemoryStore.getFeedbacks` and