@ecency/sdk 2.3.67 → 2.3.68

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.
@@ -3808,7 +3808,14 @@ interface ProMembersResponse {
3808
3808
  /**
3809
3809
  * Public, cached roster of Ecency Pro members. Backed by a lightweight private-api
3810
3810
  * endpoint (no auth) so any surface can decorate a username with a Pro badge without
3811
- * a per-user request. The list changes slowly, so it stays fresh for ~5 minutes.
3811
+ * a per-user request.
3812
+ *
3813
+ * `staleTime` is deliberately shorter than the endpoint's own cache window and is
3814
+ * NOT raised to match it. react-query has no idea how old a response already was
3815
+ * when `fetch` served it from the browser cache: it treats a nine-minute-old
3816
+ * cached body as freshly fetched and starts its own window from zero. Worst-case
3817
+ * staleness is therefore the endpoint's window plus this one, so raising this to
3818
+ * match the server would roughly double it rather than align it.
3812
3819
  */
3813
3820
  declare function getProMembersQueryOptions(): _tanstack_react_query.OmitKeyof<_tanstack_react_query.UseQueryOptions<ProMembersResponse, Error, ProMembersResponse, string[]>, "queryFn"> & {
3814
3821
  queryFn?: _tanstack_react_query.QueryFunction<ProMembersResponse, string[], never> | undefined;
@@ -4191,6 +4198,21 @@ declare function getDeletedEntryQueryOptions(author: string, permlink: string):
4191
4198
  };
4192
4199
  };
4193
4200
 
4201
+ /**
4202
+ * Tips for a single post.
4203
+ *
4204
+ * Addressed as a GET so the response can be cached. This was a POST, which no
4205
+ * cache may store, so the same tip totals were refetched on every mount. The
4206
+ * endpoint keys off nothing but author and permlink and needs no auth, and now
4207
+ * serves a Cache-Control, so a repeat read can come from the browser instead of
4208
+ * the network.
4209
+ *
4210
+ * `staleTime` is kept at or below the endpoint's own cache window rather than
4211
+ * extending it. react-query cannot see how old a response already was when
4212
+ * `fetch` served it from the browser cache, so it restarts its window from zero
4213
+ * on a body that may already be near expiry; worst-case staleness is the two
4214
+ * windows added together.
4215
+ */
4194
4216
  declare function getPostTipsQueryOptions(author: string, permlink: string, isEnabled?: boolean): _tanstack_react_query.OmitKeyof<_tanstack_react_query.UseQueryOptions<PostTipsResponse, Error, PostTipsResponse, string[]>, "queryFn"> & {
4195
4217
  queryFn?: _tanstack_react_query.QueryFunction<PostTipsResponse, string[], never> | undefined;
4196
4218
  } & {