@fncts/observable 0.0.26 → 0.0.28

package/_src/config.ts

@@ -0,0 +1,40 @@
+import type { Notification } from "./Notification.js";
+
+/**
+ * The {@link GlobalConfig} object for RxJS. It is used to configure things
+ * like how to react on unhandled errors.
+ */
+export const config: GlobalConfig = {
+  onUnhandledError: null,
+  onStoppedNotification: null,
+};
+
+/**
+ * The global configuration object for RxJS, used to configure things
+ * like how to react on unhandled errors. Accessible via {@link config}
+ * object.
+ */
+export interface GlobalConfig {
+  /**
+   * A registration point for unhandled errors from RxJS. These are errors that
+   * cannot were not handled by consuming code in the usual subscription path. For
+   * example, if you have this configured, and you subscribe to an observable without
+   * providing an error handler, errors from that subscription will end up here. This
+   * will _always_ be called asynchronously on another job in the runtime. This is because
+   * we do not want errors thrown in this user-configured handler to interfere with the
+   * behavior of the library.
+   */
+  onUnhandledError: (<E>(err: Cause<E>) => void) | null;
+
+  /**
+   * A registration point for notifications that cannot be sent to subscribers because they
+   * have completed, errored or have been explicitly unsubscribed. By default, next, complete
+   * and error notifications sent to stopped subscribers are noops. However, sometimes callers
+   * might want a different behavior. For example, with sources that attempt to report errors
+   * to stopped subscribers, a caller can configure RxJS to throw an unhandled error instead.
+   * This will _always_ be called asynchronously on another job in the runtime. This is because
+   * we do not want errors thrown in this user-configured handler to interfere with the
+   * behavior of the library.
+   */
+  onStoppedNotification: (<E, A>(notification: Notification<E, A>, subscriber: Subscriber<E, A>) => void) | null;
+}

package/_src/global.ts

@@ -103,7 +103,7 @@ import { AsyncSubject } from "@fncts/observable/Subject";
 /**
  * @tsplus global
  */
-import { isSubscriber, SafeSubscriber, Subscriber } from "@fncts/observable/Subscriber";
+import { isSubscriber, Subscriber } from "@fncts/observable/Subscriber";
 /**
  * @tsplus global
  */

package/config.d.ts

@@ -0,0 +1,36 @@
+import { Cause } from "@fncts/base/data/Cause/definition";
+import { Subscriber } from "@fncts/observable/Subscriber";
+import type { Notification } from "./Notification.js";
+/**
+ * The {@link GlobalConfig} object for RxJS. It is used to configure things
+ * like how to react on unhandled errors.
+ */
+export declare const config: GlobalConfig;
+/**
+ * The global configuration object for RxJS, used to configure things
+ * like how to react on unhandled errors. Accessible via {@link config}
+ * object.
+ */
+export interface GlobalConfig {
+    /**
+     * A registration point for unhandled errors from RxJS. These are errors that
+     * cannot were not handled by consuming code in the usual subscription path. For
+     * example, if you have this configured, and you subscribe to an observable without
+     * providing an error handler, errors from that subscription will end up here. This
+     * will _always_ be called asynchronously on another job in the runtime. This is because
+     * we do not want errors thrown in this user-configured handler to interfere with the
+     * behavior of the library.
+     */
+    onUnhandledError: (<E>(err: Cause<E>) => void) | null;
+    /**
+     * A registration point for notifications that cannot be sent to subscribers because they
+     * have completed, errored or have been explicitly unsubscribed. By default, next, complete
+     * and error notifications sent to stopped subscribers are noops. However, sometimes callers
+     * might want a different behavior. For example, with sources that attempt to report errors
+     * to stopped subscribers, a caller can configure RxJS to throw an unhandled error instead.
+     * This will _always_ be called asynchronously on another job in the runtime. This is because
+     * we do not want errors thrown in this user-configured handler to interfere with the
+     * behavior of the library.
+     */
+    onStoppedNotification: (<E, A>(notification: Notification<E, A>, subscriber: Subscriber<E, A>) => void) | null;
+}

package/global.d.ts

@@ -93,7 +93,7 @@ import { AsyncSubject } from "@fncts/observable/Subject";
 /**
  * @tsplus global
  */
-import { isSubscriber, SafeSubscriber, Subscriber } from "@fncts/observable/Subscriber";
+import { isSubscriber, Subscriber } from "@fncts/observable/Subscriber";
 /**
  * @tsplus global
  */

package/package.json

@@ -1,15 +1,17 @@
 {
   "name": "@fncts/observable",
-  "version": "0.0.26",
+  "version": "0.0.28",
   "dependencies": {
-    "@fncts/base": "0.0.37"
+    "@fncts/base": "0.0.39"
   },
   "exports": {
     "./*": {
+      "types": "./*.d.ts",
       "import": "./_mjs/*.mjs",
       "require": "./_cjs/*.cjs"
     },
     ".": {
+      "types": "./index.d.ts",
       "import": "./_mjs/index.mjs",
       "require": "./_cjs/index.cjs"
     }