@dronedeploy/rocos-js-sdk 4.4.9 → 4.4.11

package/cjs/models/gamepad/GamepadConfig.d.ts

@@ -57,12 +57,9 @@ export interface GamepadButtonRef {
     type: GamepadButtonType;
     text: string;
 }
-export interface GamepadAction {
+export interface GamepadActionBase {
     name: string;
     source: GamepadButtonRef;
-    commandId: string;
-    /** Absent on configs saved before Commands V2 existed. */
-    commandVersion?: GamepadCommandVersion;
     triggerType: GamepadTriggerType;
     /** Milliseconds between repeats. Only meaningful for `continuously`. */
     frequency: number;
@@ -76,6 +73,26 @@ export interface GamepadAction {
      */
     modifiers?: GamepadButtonRef[];
 }
+export type GamepadActionType = 'robot' | 'dashboard';
+/** A robot-side action. `actionType` is absent on configurations saved before destinations existed. */
+export interface GamepadRobotAction extends GamepadActionBase {
+    actionType?: 'robot';
+    commandId: string;
+    /** Absent on configs saved before Commands V2 existed. */
+    commandVersion?: GamepadCommandVersion;
+}
+/** A semantic action broadcast to widgets mounted on the current dashboard page. */
+export interface GamepadDashboardAction extends GamepadActionBase {
+    actionType: 'dashboard';
+    actionName: string;
+    /** Custom-widget bundles that predate destinations skip any action without a `commandId`, so it must stay absent. */
+    commandId?: never;
+    commandVersion?: never;
+}
+export type GamepadAction = GamepadRobotAction | GamepadDashboardAction;
+/** Prefer this over checking `actionType === 'robot'`, which misses configurations saved before destinations existed. */
+export declare const isGamepadRobotAction: (action: GamepadAction) => action is GamepadRobotAction;
+export declare const isGamepadDashboardAction: (action: GamepadAction) => action is GamepadDashboardAction;
 export interface GamepadVariable {
     name: string;
     source: GamepadButtonRef;

package/cjs/models/gamepad/GamepadConfig.js

@@ -1,6 +1,6 @@
 "use strict";
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.GamepadCommandVersion = exports.GamepadTriggerType = exports.MODIFIER_RELEASE_FRACTION = exports.DEFAULT_MODIFIER_THRESHOLD = exports.GamepadButtonType = void 0;
+exports.isGamepadDashboardAction = exports.isGamepadRobotAction = exports.GamepadCommandVersion = exports.GamepadTriggerType = exports.MODIFIER_RELEASE_FRACTION = exports.DEFAULT_MODIFIER_THRESHOLD = exports.GamepadButtonType = void 0;
 // Ref: https://github.com/alaingilbert/GamepadJs
 var GamepadButtonType;
 (function (GamepadButtonType) {
@@ -55,3 +55,12 @@ var GamepadCommandVersion;
     GamepadCommandVersion["COMMANDS_V2"] = "commands-v2";
     GamepadCommandVersion["RUN_JS"] = "run-js";
 })(GamepadCommandVersion || (exports.GamepadCommandVersion = GamepadCommandVersion = {}));
+/** Prefer this over checking `actionType === 'robot'`, which misses configurations saved before destinations existed. */
+const isGamepadRobotAction = (action) => {
+    return action.actionType !== 'dashboard';
+};
+exports.isGamepadRobotAction = isGamepadRobotAction;
+const isGamepadDashboardAction = (action) => {
+    return action.actionType === 'dashboard';
+};
+exports.isGamepadDashboardAction = isGamepadDashboardAction;

package/cjs/services/robot-status/connectivity.d.ts

@@ -3,7 +3,8 @@ import { Observable } from 'rxjs';
 /**
  * Service id → public path prefix, for services that expose the standard
  * `connections` endpoint. New services adopting the convention are added here.
- * The `telemetry` (Teletubby) endpoint joins this once built — see EAI-718/719.
+ * `robot-telemetry` is Teletubby's broker-side view (is the robot's telemetry
+ * stream connected), distinct from `telemetry-liveness` (is telemetry arriving).
  */
 export declare const CONNECTION_SERVICE_PREFIXES: Record<string, string>;
 /**
@@ -12,10 +13,7 @@ export declare const CONNECTION_SERVICE_PREFIXES: Record<string, string>;
  * the caller). See `getTelemetryLiveness`.
  */
 export declare const TELEMETRY_LIVENESS_SERVICE = "telemetry-liveness";
-/**
- * The services evaluated by default. The `telemetry` connections endpoint joins
- * this list once Teletubby exposes it (follow-up).
- */
+/** The services evaluated by default. */
 export declare const DEFAULT_EXPECTED_SERVICES: string[];
 /**
  * Floor for the connections-endpoint poll interval. Guards against a caller

package/cjs/services/robot-status/connectivity.js

@@ -8,11 +8,13 @@ const formatServiceUrl_1 = require("../../helpers/formatServiceUrl");
 /**
  * Service id → public path prefix, for services that expose the standard
  * `connections` endpoint. New services adopting the convention are added here.
- * The `telemetry` (Teletubby) endpoint joins this once built — see EAI-718/719.
+ * `robot-telemetry` is Teletubby's broker-side view (is the robot's telemetry
+ * stream connected), distinct from `telemetry-liveness` (is telemetry arriving).
  */
 exports.CONNECTION_SERVICE_PREFIXES = {
     'robot-configs': 'robot-configs',
     'robot-services': 'robot-services',
+    'robot-telemetry': 'telemetry',
 };
 /**
  * The telemetry-liveness signal is derived from heartbeat freshness rather than
@@ -20,11 +22,13 @@ exports.CONNECTION_SERVICE_PREFIXES = {
  * the caller). See `getTelemetryLiveness`.
  */
 exports.TELEMETRY_LIVENESS_SERVICE = 'telemetry-liveness';
-/**
- * The services evaluated by default. The `telemetry` connections endpoint joins
- * this list once Teletubby exposes it (follow-up).
- */
-exports.DEFAULT_EXPECTED_SERVICES = [exports.TELEMETRY_LIVENESS_SERVICE, 'robot-configs', 'robot-services'];
+/** The services evaluated by default. */
+exports.DEFAULT_EXPECTED_SERVICES = [
+    exports.TELEMETRY_LIVENESS_SERVICE,
+    'robot-configs',
+    'robot-services',
+    'robot-telemetry',
+];
 const DEFAULT_CONNECTIVITY_POLL_MS = 5000;
 /**
  * Floor for the connections-endpoint poll interval. Guards against a caller

package/esm/models/gamepad/GamepadConfig.d.ts

@@ -57,12 +57,9 @@ export interface GamepadButtonRef {
     type: GamepadButtonType;
     text: string;
 }
-export interface GamepadAction {
+export interface GamepadActionBase {
     name: string;
     source: GamepadButtonRef;
-    commandId: string;
-    /** Absent on configs saved before Commands V2 existed. */
-    commandVersion?: GamepadCommandVersion;
     triggerType: GamepadTriggerType;
     /** Milliseconds between repeats. Only meaningful for `continuously`. */
     frequency: number;
@@ -76,6 +73,26 @@ export interface GamepadAction {
      */
     modifiers?: GamepadButtonRef[];
 }
+export type GamepadActionType = 'robot' | 'dashboard';
+/** A robot-side action. `actionType` is absent on configurations saved before destinations existed. */
+export interface GamepadRobotAction extends GamepadActionBase {
+    actionType?: 'robot';
+    commandId: string;
+    /** Absent on configs saved before Commands V2 existed. */
+    commandVersion?: GamepadCommandVersion;
+}
+/** A semantic action broadcast to widgets mounted on the current dashboard page. */
+export interface GamepadDashboardAction extends GamepadActionBase {
+    actionType: 'dashboard';
+    actionName: string;
+    /** Custom-widget bundles that predate destinations skip any action without a `commandId`, so it must stay absent. */
+    commandId?: never;
+    commandVersion?: never;
+}
+export type GamepadAction = GamepadRobotAction | GamepadDashboardAction;
+/** Prefer this over checking `actionType === 'robot'`, which misses configurations saved before destinations existed. */
+export declare const isGamepadRobotAction: (action: GamepadAction) => action is GamepadRobotAction;
+export declare const isGamepadDashboardAction: (action: GamepadAction) => action is GamepadDashboardAction;
 export interface GamepadVariable {
     name: string;
     source: GamepadButtonRef;

package/esm/models/gamepad/GamepadConfig.js

@@ -52,3 +52,10 @@ export var GamepadCommandVersion;
     GamepadCommandVersion["COMMANDS_V2"] = "commands-v2";
     GamepadCommandVersion["RUN_JS"] = "run-js";
 })(GamepadCommandVersion || (GamepadCommandVersion = {}));
+/** Prefer this over checking `actionType === 'robot'`, which misses configurations saved before destinations existed. */
+export const isGamepadRobotAction = (action) => {
+    return action.actionType !== 'dashboard';
+};
+export const isGamepadDashboardAction = (action) => {
+    return action.actionType === 'dashboard';
+};

package/esm/services/robot-status/connectivity.d.ts

@@ -3,7 +3,8 @@ import { Observable } from 'rxjs';
 /**
  * Service id → public path prefix, for services that expose the standard
  * `connections` endpoint. New services adopting the convention are added here.
- * The `telemetry` (Teletubby) endpoint joins this once built — see EAI-718/719.
+ * `robot-telemetry` is Teletubby's broker-side view (is the robot's telemetry
+ * stream connected), distinct from `telemetry-liveness` (is telemetry arriving).
  */
 export declare const CONNECTION_SERVICE_PREFIXES: Record<string, string>;
 /**
@@ -12,10 +13,7 @@ export declare const CONNECTION_SERVICE_PREFIXES: Record<string, string>;
  * the caller). See `getTelemetryLiveness`.
  */
 export declare const TELEMETRY_LIVENESS_SERVICE = "telemetry-liveness";
-/**
- * The services evaluated by default. The `telemetry` connections endpoint joins
- * this list once Teletubby exposes it (follow-up).
- */
+/** The services evaluated by default. */
 export declare const DEFAULT_EXPECTED_SERVICES: string[];
 /**
  * Floor for the connections-endpoint poll interval. Guards against a caller

package/esm/services/robot-status/connectivity.js

@@ -5,11 +5,13 @@ import { formatServiceUrl } from '../../helpers/formatServiceUrl';
 /**
  * Service id → public path prefix, for services that expose the standard
  * `connections` endpoint. New services adopting the convention are added here.
- * The `telemetry` (Teletubby) endpoint joins this once built — see EAI-718/719.
+ * `robot-telemetry` is Teletubby's broker-side view (is the robot's telemetry
+ * stream connected), distinct from `telemetry-liveness` (is telemetry arriving).
  */
 export const CONNECTION_SERVICE_PREFIXES = {
     'robot-configs': 'robot-configs',
     'robot-services': 'robot-services',
+    'robot-telemetry': 'telemetry',
 };
 /**
  * The telemetry-liveness signal is derived from heartbeat freshness rather than
@@ -17,11 +19,13 @@ export const CONNECTION_SERVICE_PREFIXES = {
  * the caller). See `getTelemetryLiveness`.
  */
 export const TELEMETRY_LIVENESS_SERVICE = 'telemetry-liveness';
-/**
- * The services evaluated by default. The `telemetry` connections endpoint joins
- * this list once Teletubby exposes it (follow-up).
- */
-export const DEFAULT_EXPECTED_SERVICES = [TELEMETRY_LIVENESS_SERVICE, 'robot-configs', 'robot-services'];
+/** The services evaluated by default. */
+export const DEFAULT_EXPECTED_SERVICES = [
+    TELEMETRY_LIVENESS_SERVICE,
+    'robot-configs',
+    'robot-services',
+    'robot-telemetry',
+];
 const DEFAULT_CONNECTIVITY_POLL_MS = 5000;
 /**
  * Floor for the connections-endpoint poll interval. Guards against a caller

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@dronedeploy/rocos-js-sdk",
-  "version": "4.4.9",
+  "version": "4.4.11",
   "description": "Javascript SDK for rocos",
   "main": "cjs/index.js",
   "module": "esm/index.js",