hive-react-kit 0.9.0 → 0.9.1

package/dist/services/userService.d.ts

@@ -2,6 +2,19 @@ import { Follower, Following, UserProfileResponse, Account } from "@/types/user"
 import { Post } from "@/types/post";
 import type { Poll } from "@/types/poll";
 import type { PendingAuthorRow, PendingCurationRow } from "@/types/reward";
+/** Default "parent" container for getUserSnaps (kept for backwards compatibility). */
+export declare const DEFAULT_SNAP_PARENT = "peak.snaps";
+/**
+ * Known snap-container parents supported by UserDetailProfile's segmented
+ * control. Values are the account names queried via `?parent=<account>`.
+ */
+export declare const SNAP_SUBTYPE_PARENTS: {
+    readonly snaps: "peak.snaps";
+    readonly ecency: "ecency.waves";
+    readonly threads: "leothreads";
+    readonly liketu: "liketu.moments";
+};
+export type SnapSubType = keyof typeof SNAP_SUBTYPE_PARENTS;
 declare class UserService {
     private readonly HIVE_API_URL;
     /** Central fetch wrapper — threads AbortSignal to every network request */
@@ -19,10 +32,15 @@ declare class UserService {
     getUserComments(username: string, limit?: number, startAuthor?: string, startPermlink?: string, signal?: AbortSignal): Promise<Post[]>;
     getUserReplies(username: string, limit?: number, startAuthor?: string, startPermlink?: string, signal?: AbortSignal): Promise<Post[]>;
     /**
-     * Fetch snap references for a user from PeakD API.
-     * Returns { id, author, permlink }[] with cursor for pagination.
+     * Fetch snap references for a user from the hreplier API.
+     * Returns `{ id, author, permlink }[]`. The endpoint does not support
+     * cursor-based pagination — it returns a single batch, so `startId`
+     * is accepted for call-site compatibility but ignored.
+     *
+     * `parent` selects the container account: `peak.snaps` (Snaps), `ecency.waves`
+     * (Ecency waves), `leothreads` (Threads), `liketu.moments` (Liketu moments).
      */
-    getSnapReferences(username: string, startId?: number, signal?: AbortSignal): Promise<{
+    getSnapReferences(username: string, _startId?: number, signal?: AbortSignal, parent?: string): Promise<{
         id: number;
         author: string;
         permlink: string;
@@ -33,11 +51,24 @@ declare class UserService {
      */
     private batchGetPosts;
     /**
-     * Fetch snaps for a user using PeakD API + Hive bridge.get_post.
-     * Step 1: Get snap references from PeakD (with pagination via startId)
-     * Step 2: Batch fetch full post data via bridge.get_post
+     * Fetch a page of snaps for a user via the hreplier API + Hive bridge.get_post.
+     *
+     * The hreplier endpoint returns the full snap-reference list in one shot and
+     * has no server-side pagination, so we cache it per (username, parent) and
+     * slice client-side. `startId` is repurposed as the slice offset (20-item
+     * pages):
+     *   - undefined / 0 → first 20 refs
+     *   - 20, 40, …     → subsequent pages
+     * `nextStartId` is the next offset to request, or null when exhausted.
+     *
+     * `parent` selects the container account — see SNAP_SUBTYPE_PARENTS
+     * (defaults to `peak.snaps`). Cache is keyed per parent so switching
+     * segments never collides.
+     *
+     * Only the current slice is materialised via bridge.get_post, so switching
+     * pages stays snappy.
      */
-    getUserSnaps(username: string, startId?: number, observer?: string, signal?: AbortSignal): Promise<{
+    getUserSnaps(username: string, startId?: number, observer?: string, signal?: AbortSignal, parent?: string): Promise<{
         snaps: Post[];
         nextStartId: number | null;
     }>;

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "hive-react-kit",
   "private": false,
-  "version": "0.9.0",
+  "version": "0.9.1",
   "type": "module",
   "main": "./dist/index.cjs.js",
   "module": "./dist/index.esm.js",