@hotmeshio/hotmesh 0.1.7 → 0.1.8

package/README.md

@@ -295,31 +295,31 @@ const hotMesh = await HotMesh.init({
 ```
 
 ### Observability
-Workflows and activities are run according to the rules you define, offering [Graph-Oriented](https://github.com/hotmeshio/sdk-typescript/blob/main/docs/system_lifecycle.md#telemetry) telemetry insights into your legacy function executions.
+Workflows and activities are run according to the rules you define, offering [Graph-Oriented](https://github.com/hotmeshio/sdk-typescript/tree/main/docs/system_lifecycle.md#telemetry) telemetry insights into your legacy function executions.
 
 ## FAQ
-Refer to the [FAQ](https://github.com/hotmeshio/sdk-typescript/blob/main/docs/faq.md) for terminology, definitions, and an exploration of how HotMesh facilitates orchestration use cases.
+Refer to the [FAQ](https://github.com/hotmeshio/sdk-typescript/tree/main/docs/faq.md) for terminology, definitions, and an exploration of how HotMesh facilitates orchestration use cases.
 
 ## Quick Start
-Refer to the [Quick Start](https://github.com/hotmeshio/sdk-typescript/blob/main/docs/quickstart.md) for sample YAML workflows you can copy, paste, and modify to get started.
+Refer to the [Quick Start](https://github.com/hotmeshio/sdk-typescript/tree/main/docs/quickstart.md) for sample YAML workflows you can copy, paste, and modify to get started.
 
 ## Developer Guide
-For more details on the complete development process, including information about schemas, APIs, and deployment, consult the [Developer Guide](https://github.com/hotmeshio/sdk-typescript/blob/main/docs/developer_guide.md).
+For more details on the complete development process, including information about schemas, APIs, and deployment, consult the [Developer Guide](https://github.com/hotmeshio/sdk-typescript/tree/main/docs/developer_guide.md).
 
 ## Model Driven Development
-[Model Driven Development](https://github.com/hotmeshio/sdk-typescript/blob/main/docs/model_driven_development.md) is an established strategy for managing process-oriented tasks. Check out this guide to understand its foundational principles.
+[Model Driven Development](https://github.com/hotmeshio/sdk-typescript/tree/main/docs/model_driven_development.md) is an established strategy for managing process-oriented tasks. Check out this guide to understand its foundational principles.
 
 ## Data Mapping
-Exchanging data between activities is central to HotMesh. For detailed information on supported functions and the functional mapping syntax (@pipes), see the [Data Mapping Overview](https://github.com/hotmeshio/sdk-typescript/blob/main/docs/data_mapping.md).
+Exchanging data between activities is central to HotMesh. For detailed information on supported functions and the functional mapping syntax (@pipes), see the [Data Mapping Overview](https://github.com/hotmeshio/sdk-typescript/tree/main/docs/data_mapping.md).
 
 ## Composition
-While the simplest graphs are linear, detailing a consistent sequence of non-cyclical activities, graphs can be layered to represent intricate business scenarios. Some can even be designed to accommodate long-lasting workflows that span months. For more details, check out the [Composable Workflow Guide](https://github.com/hotmeshio/sdk-typescript/blob/main/docs/composable_workflow.md).
+While the simplest graphs are linear, detailing a consistent sequence of non-cyclical activities, graphs can be layered to represent intricate business scenarios. Some can even be designed to accommodate long-lasting workflows that span months. For more details, check out the [Composable Workflow Guide](https://github.com/hotmeshio/sdk-typescript/tree/main/docs/composable_workflow.md).
 
 ## System Lifecycle
-Gain insight into HotMesh's monitoring, exception handling, and alarm configurations via the [System Lifecycle Guide](https://github.com/hotmeshio/sdk-typescript/blob/main/docs/system_lifecycle.md).
+Gain insight into HotMesh's monitoring, exception handling, and alarm configurations via the [System Lifecycle Guide](https://github.com/hotmeshio/sdk-typescript/tree/main/docs/system_lifecycle.md).
 
 ## Distributed Orchestration | System Overview
-HotMesh is a distributed orchestration engine. Refer to the [Distributed Orchestration Guide](https://github.com/hotmeshio/sdk-typescript/blob/main/docs/distributed_orchestration.md) for a high-level overview of the approach.
+HotMesh is a distributed orchestration engine. Refer to the [Distributed Orchestration Guide](https://github.com/hotmeshio/sdk-typescript/tree/main/docs/distributed_orchestration.md) for a high-level overview of the approach.
 
 ## Distributed Orchestration | System Design
 HotMesh is more than Redis and TypeScript. The theory that underlies the architecture is applicable to any number of data storage and streaming backends: [A Message-Oriented Approach to Decentralized Process Orchestration](https://zenodo.org/records/12168558).

package/build/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@hotmeshio/hotmesh",
-    "version": "0.1.7",
+    "version": "0.1.8",
     "description": "Unbreakable Workflows",
     "main": "./build/index.js",
     "types": "./build/index.d.ts",

package/build/services/durable/client.js

@@ -19,10 +19,11 @@ class ClientService {
         this.getHotMeshClient = async (workflowTopic, namespace) => {
             const targetNS = namespace ?? factory_1.APP_ID;
             if (ClientService.instances.has(targetNS)) {
+                const targetTopic = `${namespace ?? factory_1.APP_ID}.${workflowTopic}`;
                 const hotMeshClient = await ClientService.instances.get(targetNS);
                 await this.verifyWorkflowActive(hotMeshClient, targetNS);
-                if (!ClientService.topics.includes(workflowTopic)) {
-                    ClientService.topics.push(workflowTopic);
+                if (!ClientService.topics.includes(targetTopic)) {
+                    ClientService.topics.push(targetTopic);
                     await ClientService.createStream(hotMeshClient, workflowTopic, namespace);
                 }
                 return hotMeshClient;
@@ -205,11 +206,12 @@ ClientService.createStream = async (hotMeshClient, workflowTopic, namespace) =>
  * exists and if not, create it.
  */
 ClientService.verifyStream = async (workflowTopic, namespace) => {
+    const targetTopic = `${namespace ?? factory_1.APP_ID}.${workflowTopic}`;
     const targetNS = namespace ?? factory_1.APP_ID;
     if (ClientService.instances.has(targetNS)) {
         const hotMeshClient = await ClientService.instances.get(targetNS);
-        if (!ClientService.topics.includes(workflowTopic)) {
-            ClientService.topics.push(workflowTopic);
+        if (!ClientService.topics.includes(targetTopic)) {
+            ClientService.topics.push(targetTopic);
             await ClientService.createStream(hotMeshClient, workflowTopic, namespace);
         }
         return hotMeshClient;

package/build/services/durable/worker.d.ts

@@ -2,11 +2,12 @@ import { HotMeshService as HotMesh } from '../hotmesh';
 import { Connection, Registry, WorkerConfig, WorkerOptions } from '../../types/durable';
 export declare class WorkerService {
     static activityRegistry: Registry;
-    static connection: Connection;
+    static connections: Map<string, import("../../types/durable").ConnectionConfig>;
     static instances: Map<string, HotMesh | Promise<HotMesh>>;
     workflowRunner: HotMesh;
     activityRunner: HotMesh;
     static getHotMesh: (workflowTopic: string, config?: Partial<WorkerConfig>, options?: WorkerOptions) => Promise<HotMesh>;
+    static findConnectionByNamespace: (namespace: string) => Connection;
     static activateWorkflow(hotMesh: HotMesh): Promise<void>;
     static registerActivities<ACT>(activities: ACT): Registry;
     static create(config: WorkerConfig): Promise<WorkerService>;

package/build/services/durable/worker.js

@@ -58,7 +58,8 @@ class WorkerService {
         return WorkerService.activityRegistry;
     }
     static async create(config) {
-        WorkerService.connection = config.connection;
+        const targetNamespace = config.namespace ?? factory_1.APP_ID;
+        WorkerService.connections.set(targetNamespace, config.connection);
         const workflow = config.workflow;
         const [workflowFunctionName, workflowFunction] = WorkerService.resolveWorkflowTarget(workflow);
         const baseTopic = `${config.taskQueue}-${workflowFunctionName}`;
@@ -371,20 +372,37 @@ class WorkerService {
 }
 _a = WorkerService;
 WorkerService.activityRegistry = {}; //user's activities
+WorkerService.connections = new Map();
 WorkerService.instances = new Map();
 WorkerService.getHotMesh = async (workflowTopic, config, options) => {
-    if (WorkerService.instances.has(workflowTopic)) {
-        return await WorkerService.instances.get(workflowTopic);
+    const targetNamespace = config?.namespace ?? factory_1.APP_ID;
+    const targetTopic = `${targetNamespace}.${workflowTopic}`;
+    if (WorkerService.instances.has(targetTopic)) {
+        return await WorkerService.instances.get(targetTopic);
     }
     const hotMeshClient = hotmesh_1.HotMeshService.init({
         logLevel: options?.logLevel ?? enums_1.HMSH_LOGLEVEL,
-        appId: config.namespace ?? factory_1.APP_ID,
-        engine: { redis: { ...WorkerService.connection } },
+        appId: targetNamespace,
+        engine: {
+            redis: { ...WorkerService.findConnectionByNamespace(targetNamespace) },
+        },
     });
-    WorkerService.instances.set(workflowTopic, hotMeshClient);
+    WorkerService.instances.set(targetTopic, hotMeshClient);
     await WorkerService.activateWorkflow(await hotMeshClient);
     return hotMeshClient;
 };
+WorkerService.findConnectionByNamespace = (namespace) => {
+    let defaultConnection;
+    for (const [ns, value] of WorkerService.connections) {
+        if (ns === namespace) {
+            return value;
+        }
+        else if (!defaultConnection) {
+            defaultConnection = value;
+        }
+    }
+    return defaultConnection;
+};
 WorkerService.Context = {
     info: () => {
         return {

package/build/types/index.d.ts

@@ -7,7 +7,7 @@ export { ActivityConfig, ActivityWorkflowDataType, ChildResponseType, ClientConf
 export { DurableChildErrorType, DurableProxyErrorType, DurableSleepErrorType, DurableWaitForAllErrorType, DurableWaitForErrorType, } from './error';
 export { ActivityAction, DependencyExport, DurableJobExport, ExportCycles, ExportItem, ExportOptions, ExportTransitions, JobAction, JobExport, JobActionExport, JobTimeline, } from './exporter';
 export { HookCondition, HookConditions, HookGate, HookInterface, HookRule, HookRules, HookSignal, } from './hook';
-export { ILogger } from './logger';
+export { ILogger, LogLevel, } from './logger';
 export { ExtensionType, JobCompletionOptions, JobData, JobsData, JobInterruptOptions, JobMetadata, JobOutput, JobState, JobStatus, PartialJobState, } from './job';
 export { MappingStatements } from './map';
 export { Pipe, PipeContext, PipeItem, PipeItems, PipeObject, ReduceObject, } from './pipe';

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@hotmeshio/hotmesh",
-  "version": "0.1.7",
+  "version": "0.1.8",
   "description": "Unbreakable Workflows",
   "main": "./build/index.js",
   "types": "./build/index.d.ts",

package/types/index.ts

@@ -77,7 +77,10 @@ export {
   HookRules,
   HookSignal,
 } from './hook';
-export { ILogger } from './logger';
+export {
+  ILogger,
+  LogLevel,
+} from './logger';
 export {
   ExtensionType,
   JobCompletionOptions,