@cripty2001/utils 0.0.167 → 0.0.168

package/dist/react-whispr.d.ts

@@ -161,6 +161,7 @@ export type AsyncInputValue<C extends Record<string, JSONEncodable>, R extends R
  * @param value - Current external value containing both result data and metadata with config/timestamp. Metadata should be considered opaque, and always carried araoud as they are
  * @param setValue - Callback to update external value when async operations complete
  * @param handler - Async function that computes results from config.
+ * @param setPending? - Callback to check if the async operation is in flight or ended. If this is called with false, setValue has already been called with the latest result. To avoid concurrency problems, setValue is always called BEFORE calling this with false. No assumption be made for call with true. Please note that this function may be called rapidly even without real updates. The only assumption that should be made about this is the fact that once it is called with false, the value is guaranteed to be the latest reported one, until a call with true. A call with true may means that the value is outdated, or maybe no. There is simply no guarantee about the result when this value is true.
  *
  * @returns Array containing:
  *   - `value`: Current config (updates synchronously with user input)
@@ -193,7 +194,7 @@ export type AsyncInputValue<C extends Record<string, JSONEncodable>, R extends R
  * The returned `result` will lag behind `value` during async processing. Consider showing a loader or some other similar indication
  * Handler is NOT reactive. Conceptually it is a pure function that derives an async status from the value input, so there is no reason for it to be reactive, and this saves a lot heachaches with react reactivity loops.
  */
-export declare function useAsyncInput<C extends Record<string, JSONEncodable>, R extends Record<string, JSONEncodable>>(value: AsyncInputValue<C, R>, setValue: (value: AsyncInputValue<C, R>) => void, handler: (config: C) => Promise<R>): [
+export declare function useAsyncInput<C extends Record<string, JSONEncodable>, R extends Record<string, JSONEncodable>>(value: AsyncInputValue<C, R>, setValue: (value: AsyncInputValue<C, R>) => void, handler: (config: C) => Promise<R>, setPending: (pending: boolean) => void): [
     value: C,
     setValue: (updater: (draft: C) => C | void) => void,
     result: R | null

package/dist/react-whispr.js

@@ -321,6 +321,7 @@ function useSafeRef(value) {
  * @param value - Current external value containing both result data and metadata with config/timestamp. Metadata should be considered opaque, and always carried araoud as they are
  * @param setValue - Callback to update external value when async operations complete
  * @param handler - Async function that computes results from config.
+ * @param setPending? - Callback to check if the async operation is in flight or ended. If this is called with false, setValue has already been called with the latest result. To avoid concurrency problems, setValue is always called BEFORE calling this with false. No assumption be made for call with true. Please note that this function may be called rapidly even without real updates. The only assumption that should be made about this is the fact that once it is called with false, the value is guaranteed to be the latest reported one, until a call with true. A call with true may means that the value is outdated, or maybe no. There is simply no guarantee about the result when this value is true.
  *
  * @returns Array containing:
  *   - `value`: Current config (updates synchronously with user input)
@@ -353,11 +354,14 @@ function useSafeRef(value) {
  * The returned `result` will lag behind `value` during async processing. Consider showing a loader or some other similar indication
  * Handler is NOT reactive. Conceptually it is a pure function that derives an async status from the value input, so there is no reason for it to be reactive, and this saves a lot heachaches with react reactivity loops.
  */
-function useAsyncInput(value, setValue, handler) {
+function useAsyncInput(value, setValue, handler, setPending) {
     const [meta, setMeta] = (0, react_1.useState)({
         config: value._meta.config,
         ts: value._meta.ts
     });
+    (0, react_1.useEffect)(() => {
+        setPending(true);
+    }, [meta, setPending]);
     (0, react_1.useEffect)(() => {
         if (value._meta.ts > meta.ts) {
             setMeta(value._meta);
@@ -378,9 +382,10 @@ function useAsyncInput(value, setValue, handler) {
         if (result === null)
             return;
         if (result._meta.ts <= value._meta.ts)
-            return;
+            return setPending(false); // Value is already updated, but we still need to clear the pending state. Also, we can't just update the value, as it will cause loops.
         setValue(result);
-    }, [result, value, setValue]);
+        setPending(false);
+    }, [result, value, setValue, setPending]);
     const returnedSetValue = (0, react_1.useCallback)((updater) => {
         const cloned = structuredClone(meta.config);
         const new_data = updater(cloned);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cripty2001/utils",
-  "version": "0.0.167",
+  "version": "0.0.168",
   "description": "Internal Set of utils. If you need them use them, otherwise go to the next package ;)",
   "homepage": "https://github.com/cripty2001/utils#readme",
   "bugs": {