@solvice/routing 0.17.7-beta.0 → 0.17.9-beta.0

package/dist/runs.d.ts

@@ -1158,7 +1158,7 @@ export interface components {
          *       "type": "sequence"
          *     }
          */
-        Relation: components["schemas"]["RelationSequence"] | components["schemas"]["RelationTagOrder"] | components["schemas"]["RelationSameVehicle"] | components["schemas"]["RelationSameDay"] | components["schemas"]["RelationSameRoute"] | components["schemas"]["RelationSynchronized"] | components["schemas"]["RelationTimeLag"] | components["schemas"]["RelationCompatibleVehicles"] | components["schemas"]["RelationAllOrNone"];
+        Relation: components["schemas"]["RelationSequence"] | components["schemas"]["RelationConsecutive"] | components["schemas"]["RelationTagOrder"] | components["schemas"]["RelationSameVehicle"] | components["schemas"]["RelationSameDay"] | components["schemas"]["RelationSameRoute"] | components["schemas"]["RelationSynchronized"] | components["schemas"]["RelationTimeLag"] | components["schemas"]["RelationCompatibleVehicles"] | components["schemas"]["RelationAllOrNone"];
         /**
          * All or none
          * @description All or none: either every member in `stops` is served, or none is.
@@ -1216,6 +1216,29 @@ export interface components {
              */
             type: "compatible_vehicles";
         };
+        /**
+         * Consecutive
+         * @description Ordering with no gap: like `sequence`, and in addition no other stop may
+         *     sit between two neighbouring members that are served on the same
+         *     route. A member that is unassigned is skipped, so only listed
+         *     neighbours that are both served are adjacent. Members on different
+         *     routes are unconstrained; add `same_route` to keep them together.
+         */
+        RelationConsecutive: {
+            /**
+             * @description Job ids or shipment-leg stop ids, in the order they must be served
+             *     back to back. At least 2. A stop has one successor and one predecessor
+             *     across all `consecutive` relations, so `[a, b]` and `[b, c]` may
+             *     overlap but `[a, b]` and `[a, c]` may not. A shipment's own id is rejected with HTTP
+             *     400 `not_supported`.
+             */
+            stops: string[];
+            /**
+             * @description Discriminator: always `consecutive`. (enum property replaced by openapi-typescript)
+             * @enum {string}
+             */
+            type: "consecutive";
+        };
         /**
          * @description Which instant of a member a `synchronized` or `time_lag` relation is
          *     measured at, named after the response stop field that reports it. There is

package/dist/v3.d.ts

@@ -1391,7 +1391,7 @@ export interface components {
          *       "type": "sequence"
          *     }
          */
-        Relation: components["schemas"]["RelationSequence"] | components["schemas"]["RelationTagOrder"] | components["schemas"]["RelationSameVehicle"] | components["schemas"]["RelationSameDay"] | components["schemas"]["RelationSameRoute"] | components["schemas"]["RelationSynchronized"] | components["schemas"]["RelationTimeLag"] | components["schemas"]["RelationCompatibleVehicles"] | components["schemas"]["RelationAllOrNone"];
+        Relation: components["schemas"]["RelationSequence"] | components["schemas"]["RelationConsecutive"] | components["schemas"]["RelationTagOrder"] | components["schemas"]["RelationSameVehicle"] | components["schemas"]["RelationSameDay"] | components["schemas"]["RelationSameRoute"] | components["schemas"]["RelationSynchronized"] | components["schemas"]["RelationTimeLag"] | components["schemas"]["RelationCompatibleVehicles"] | components["schemas"]["RelationAllOrNone"];
         /**
          * All or none
          * @description All or none: either every member in `stops` is served, or none is.
@@ -1449,6 +1449,29 @@ export interface components {
              */
             type: "compatible_vehicles";
         };
+        /**
+         * Consecutive
+         * @description Ordering with no gap: like `sequence`, and in addition no other stop may
+         *     sit between two neighbouring members that are served on the same
+         *     route. A member that is unassigned is skipped, so only listed
+         *     neighbours that are both served are adjacent. Members on different
+         *     routes are unconstrained; add `same_route` to keep them together.
+         */
+        RelationConsecutive: {
+            /**
+             * @description Job ids or shipment-leg stop ids, in the order they must be served
+             *     back to back. At least 2. A stop has one successor and one predecessor
+             *     across all `consecutive` relations, so `[a, b]` and `[b, c]` may
+             *     overlap but `[a, b]` and `[a, c]` may not. A shipment's own id is rejected with HTTP
+             *     400 `not_supported`.
+             */
+            stops: string[];
+            /**
+             * @description Discriminator: always `consecutive`. (enum property replaced by openapi-typescript)
+             * @enum {string}
+             */
+            type: "consecutive";
+        };
         /**
          * @description Which instant of a member a `synchronized` or `time_lag` relation is
          *     measured at, named after the response stop field that reports it. There is

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@solvice/routing",
-  "version": "0.17.7-beta.0",
+  "version": "0.17.9-beta.0",
   "description": "TypeScript client for the Solvice V3 routing API, generated from its OpenAPI spec.",
   "license": "Apache-2.0",
   "homepage": "https://docs.solvice.io/guides/platform/sdks/typescript",