@transitive-sdk/utils-web 0.15.0 → 0.16.0

package/dist/utils-web.js

@@ -805,9 +805,10 @@ var require_MqttSync = __commonJS({
             if (!inclMeta && path.some((field) => field[0] == "$")) {
               return;
             }
-            if (this.rpcHandlers[topic]) {
+            const rpcHandler = this.getRPCHandler(topic);
+            if (rpcHandler) {
               const json = mqttParsePayload(payload);
-              this.handleRPCRequest(topic, json);
+              this.handleRPCRequest(path, rpcHandler, json);
             } else if (this.rpcCallbacks[topic]) {
               const json = mqttParsePayload(payload);
               this.handleRPCResponse(topic, json);
@@ -1183,12 +1184,17 @@ var require_MqttSync = __commonJS({
       /* --------------------------------------------------------------------------
       *  Remote Procedure Calls (RPC)
       */
+      /** Given a (ground) topic find the matching RPC handler, if any. This is
+      * needed because RPC topics can include wildcards. */
+      getRPCHandler(topic) {
+        return _3.find(this.rpcHandlers, (_handler, topicSelector) => topicMatch(topicSelector, topic));
+      }
       /* Handle RPC requests  */
-      async handleRPCRequest(topic, json) {
-        log2.debug("handling RPC request for", topic, json);
-        const handler = this.rpcHandlers[topic];
-        const result = handler(json.args);
-        const responseTopic = `${topic.replace("/request", "/response")}/${json.id}`;
+      async handleRPCRequest(path, handler, json) {
+        log2.debug("handling RPC request for", path, json);
+        const commandTopic = pathToTopic2(path.slice(0, -1));
+        const result = handler(json.args, commandTopic);
+        const responseTopic = `${commandTopic}/response/${json.id}`;
         if (result instanceof Promise) {
           result.then((resultValue) => this.mqtt.publish(
             responseTopic,
@@ -1211,24 +1217,29 @@ var require_MqttSync = __commonJS({
         this.mqtt.unsubscribe(topic);
       }
       /** Register an RPC request handler. Example:
-       * ```js
-       * mqttSync.register('/mySquare', arg => {
-       *   log.debug('running /mySquare with args', arg);
-       *   return arg * arg;
-       * });
-       * ```
-       * Note that the command topic needs to be in the capabilities namespace like
-       * any other topic. In robot capabilities, as usual, these can start in `/`
-       * because the local mqtt bridge operated by the robot agent will place all
-       * topics in their respective namespace. In the cloud and on the web you will
-       * need to use the respective namespace, i.e.,
-       * `/orgId/deviceId/@scope/capName/capVersion/`.
-       *
-       * #### Async/Await
-       * Yes, you can make the handler `async` and use `await` inside of it. This
-       * will be handled correctly, i.e., MqttSync will await the result of the
-       * handler before responding to the RPC request client.
-       */
+      * ```js
+      * mqttSync.register('/mySquare', (arg, commandTopic) => {
+      *   log.debug('we got request on topic', commandTopic);
+      *   log.debug('running /mySquare with args', arg);
+      *   return arg * arg;
+      * });
+      * ```
+      * Note that the command topic needs to be in the capabilities namespace like
+      * any other topic. In robot capabilities, as usual, these can start in `/`
+      * because the local mqtt bridge operated by the robot agent will place all
+      * topics in their respective namespace. In the cloud and on the web you will
+      * need to use the respective namespace, i.e.,
+      * `/orgId/deviceId/@scope/capName/capVersion/`.
+      *
+      * You can use wildcards in the registered topic. The handler will receive the
+      * actual, ground topic the request was made on as the second argument. This
+      * allows you to make the RPCs behavior depend on the topic.
+      *
+      * #### Async/Await
+      * Yes, you can make the handler `async` and use `await` inside of it. This
+      * will be handled correctly, i.e., MqttSync will await the result of the
+      * handler before responding to the RPC request client.
+      */
       register(command, handler) {
         log2.debug("registering RPC handler for", command);
         const requestTopic = `${command}/request`;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@transitive-sdk/utils-web",
-  "version": "0.15.0",
+  "version": "0.16.0",
   "description": "Web utils for the Transitive framework",
   "homepage": "https://transitiverobotics.com",
   "repository": {