@vertigis/viewer-spec 57.2.0 → 57.4.0

package/messaging/registry/Operations.d.ts

@@ -21,6 +21,7 @@ import { MeasurementOperations } from "./measurement.js";
 import { MessagingOperations } from "./messaging.js";
 import { NetworkOperations } from "./network.js";
 import { OfflineOperations } from "./offline.js";
+import { PortalOperations } from "./portal.js";
 import { ProjectOperations } from "./project.js";
 import { QueryBuilderOperations } from "./query-builder.js";
 import { ResultsOperations } from "./results.js";
@@ -52,6 +53,7 @@ export declare class Operations extends OperationRegistry {
     readonly messaging: MessagingOperations;
     readonly network: NetworkOperations;
     readonly offline: OfflineOperations;
+    readonly portal: PortalOperations;
     readonly project: ProjectOperations;
     readonly queryBuilder: QueryBuilderOperations;
     readonly sketching: SketchingOperations;

package/messaging/registry/Operations.js

@@ -1 +1 @@
-import{OperationRegistry as s}from"../OperationRegistry.js";import{AppOperations as e}from"./app.js";import{ArcadeOperations as m}from"./arcade.js";import{AuthOperations as i}from"./auth.js";import{BasemapOperations as r}from"./basemap.js";import{ChartOperations as t}from"./charts.js";import{DebugConsoleOperations as o}from"./debugConsole.js";import{DrawingOperations as a}from"./drawing.js";import{EditOperations as g}from"./edit.js";import{FileOperations as n}from"./file.js";import{FilterBuilderOperations as p}from"./filter-builder.js";import{GeocodeOperations as f}from"./geocode.js";import{GeolocationOperations as h}from"./geolocation.js";import{GeometryOperations as w}from"./geometry.js";import{HighlightsOperations as j}from"./highlights.js";import{KpiOperations as _}from"./kpi.js";import{LicensingOperations as l}from"./licensing.js";import{LogViewerOperations as u}from"./logViewer.js";import{MapOperations as c}from"./map.js";import{MeasurementOperations as d}from"./measurement.js";import{MessagingOperations as k}from"./messaging.js";import{NetworkOperations as y}from"./network.js";import{OfflineOperations as b}from"./offline.js";import{ProjectOperations as x}from"./project.js";import{QueryBuilderOperations as q}from"./query-builder.js";import{ResultsOperations as v}from"./results.js";import{SketchingOperations as B}from"./sketching.js";import{SystemOperations as C}from"./system.js";import{TasksOperations as O}from"./tasks.js";import{UIOperations as V}from"./ui.js";import{ViewerOperations as R}from"./viewer.js";import{WorkflowOperations as z}from"./workflow.js";export class Operations extends s{arcade=new m(this._messages);auth=new i(this._messages);app=new e(this._messages);basemap=new r(this._messages);charts=new t(this._messages);edit=new g(this._messages);drawing=new a(this._messages);file=new n(this._messages);filterBuilder=new p(this._messages);geocode=new f(this._messages);geolocation=new h(this._messages);geometry=new w(this._messages);highlights=new j(this._messages);kpi=new _(this._messages);licensing=new l(this._messages);logViewer=new u(this._messages);map=new c(this._messages);measurement=new d(this._messages);messaging=new k(this._messages);network=new y(this._messages);offline=new b(this._messages);project=new x(this._messages);queryBuilder=new q(this._messages);sketching=new B(this._messages);system=new C(this._messages);results=new v(this._messages);tasks=new O(this._messages);ui=new V(this._messages);viewer=new R(this._messages);workflow=new z(this._messages);debugConsole=new o(this._messages);_prefix=""}
+import{OperationRegistry as s}from"../OperationRegistry.js";import{AppOperations as e}from"./app.js";import{ArcadeOperations as m}from"./arcade.js";import{AuthOperations as i}from"./auth.js";import{BasemapOperations as r}from"./basemap.js";import{ChartOperations as t}from"./charts.js";import{DebugConsoleOperations as o}from"./debugConsole.js";import{DrawingOperations as a}from"./drawing.js";import{EditOperations as g}from"./edit.js";import{FileOperations as n}from"./file.js";import{FilterBuilderOperations as p}from"./filter-builder.js";import{GeocodeOperations as f}from"./geocode.js";import{GeolocationOperations as h}from"./geolocation.js";import{GeometryOperations as w}from"./geometry.js";import{HighlightsOperations as j}from"./highlights.js";import{KpiOperations as _}from"./kpi.js";import{LicensingOperations as l}from"./licensing.js";import{LogViewerOperations as u}from"./logViewer.js";import{MapOperations as c}from"./map.js";import{MeasurementOperations as d}from"./measurement.js";import{MessagingOperations as k}from"./messaging.js";import{NetworkOperations as y}from"./network.js";import{OfflineOperations as b}from"./offline.js";import{PortalOperations as x}from"./portal.js";import{ProjectOperations as q}from"./project.js";import{QueryBuilderOperations as v}from"./query-builder.js";import{ResultsOperations as B}from"./results.js";import{SketchingOperations as C}from"./sketching.js";import{SystemOperations as O}from"./system.js";import{TasksOperations as V}from"./tasks.js";import{UIOperations as R}from"./ui.js";import{ViewerOperations as z}from"./viewer.js";import{WorkflowOperations as A}from"./workflow.js";export class Operations extends s{arcade=new m(this._messages);auth=new i(this._messages);app=new e(this._messages);basemap=new r(this._messages);charts=new t(this._messages);edit=new g(this._messages);drawing=new a(this._messages);file=new n(this._messages);filterBuilder=new p(this._messages);geocode=new f(this._messages);geolocation=new h(this._messages);geometry=new w(this._messages);highlights=new j(this._messages);kpi=new _(this._messages);licensing=new l(this._messages);logViewer=new u(this._messages);map=new c(this._messages);measurement=new d(this._messages);messaging=new k(this._messages);network=new y(this._messages);offline=new b(this._messages);portal=new x(this._messages);project=new q(this._messages);queryBuilder=new v(this._messages);sketching=new C(this._messages);system=new O(this._messages);results=new B(this._messages);tasks=new V(this._messages);ui=new R(this._messages);viewer=new z(this._messages);workflow=new A(this._messages);debugConsole=new o(this._messages);_prefix=""}

package/messaging/schema/common-action.schema.json

@@ -10917,7 +10917,7 @@
         },
         "esri.rest-api.SubtypeGroupLayerJson.SubtypeGroupLayerJson": {
             "additionalProperties": false,
-            "description": "SubtypeGroupLayer provides the ability to organize several sublayers into one common layer. Suppose there are several FeatureLayers that all represent water features in different dimensions. For example, wells (points), streams (lines), and lakes (polygons). The SubtypeGroupLayer provides the functionality to treat them as one layer called Water Features even though they are stored as separate feature layers.\n\nSee {@link https://developers.arcgis.com/web-scene-specification/objects/subtypeGroupLayer/}.",
+            "description": "SubtypeGroupLayer provides the ability to organize several sublayers into one common layer. Suppose there are several FeatureLayers that all represent water features in different dimensions. For example, wells (points), streams (lines), and lakes (polygons). The SubtypeGroupLayer provides the functionality to treat them as one layer called Water Features even though they are stored as separate feature layers.\n\nSee {@link https://developers.arcgis.com/web-map-specification/objects/subtypeGroupLayer/}.",
             "properties": {
                 "blendMode": {
                     "description": "Blend modes are used to blend layers together to create an interesting effect in a layer, or even to produce what seems like a new layer.",

package/messaging/schema/common-event.schema.json

@@ -7198,7 +7198,7 @@
         },
         "esri.rest-api.SubtypeGroupLayerJson.SubtypeGroupLayerJson": {
             "additionalProperties": false,
-            "description": "SubtypeGroupLayer provides the ability to organize several sublayers into one common layer. Suppose there are several FeatureLayers that all represent water features in different dimensions. For example, wells (points), streams (lines), and lakes (polygons). The SubtypeGroupLayer provides the functionality to treat them as one layer called Water Features even though they are stored as separate feature layers.\n\nSee {@link https://developers.arcgis.com/web-scene-specification/objects/subtypeGroupLayer/}.",
+            "description": "SubtypeGroupLayer provides the ability to organize several sublayers into one common layer. Suppose there are several FeatureLayers that all represent water features in different dimensions. For example, wells (points), streams (lines), and lakes (polygons). The SubtypeGroupLayer provides the functionality to treat them as one layer called Water Features even though they are stored as separate feature layers.\n\nSee {@link https://developers.arcgis.com/web-map-specification/objects/subtypeGroupLayer/}.",
             "properties": {
                 "blendMode": {
                     "description": "Blend modes are used to blend layers together to create an interesting effect in a layer, or even to produce what seems like a new layer.",

package/messaging/schema/mobile-action.schema.json

@@ -12050,7 +12050,7 @@
         },
         "esri.rest-api.SubtypeGroupLayerJson.SubtypeGroupLayerJson": {
             "additionalProperties": false,
-            "description": "SubtypeGroupLayer provides the ability to organize several sublayers into one common layer. Suppose there are several FeatureLayers that all represent water features in different dimensions. For example, wells (points), streams (lines), and lakes (polygons). The SubtypeGroupLayer provides the functionality to treat them as one layer called Water Features even though they are stored as separate feature layers.\n\nSee {@link https://developers.arcgis.com/web-scene-specification/objects/subtypeGroupLayer/}.",
+            "description": "SubtypeGroupLayer provides the ability to organize several sublayers into one common layer. Suppose there are several FeatureLayers that all represent water features in different dimensions. For example, wells (points), streams (lines), and lakes (polygons). The SubtypeGroupLayer provides the functionality to treat them as one layer called Water Features even though they are stored as separate feature layers.\n\nSee {@link https://developers.arcgis.com/web-map-specification/objects/subtypeGroupLayer/}.",
             "properties": {
                 "blendMode": {
                     "description": "Blend modes are used to blend layers together to create an interesting effect in a layer, or even to produce what seems like a new layer.",

package/messaging/schema/mobile-event.schema.json

@@ -8755,7 +8755,7 @@
         },
         "esri.rest-api.SubtypeGroupLayerJson.SubtypeGroupLayerJson": {
             "additionalProperties": false,
-            "description": "SubtypeGroupLayer provides the ability to organize several sublayers into one common layer. Suppose there are several FeatureLayers that all represent water features in different dimensions. For example, wells (points), streams (lines), and lakes (polygons). The SubtypeGroupLayer provides the functionality to treat them as one layer called Water Features even though they are stored as separate feature layers.\n\nSee {@link https://developers.arcgis.com/web-scene-specification/objects/subtypeGroupLayer/}.",
+            "description": "SubtypeGroupLayer provides the ability to organize several sublayers into one common layer. Suppose there are several FeatureLayers that all represent water features in different dimensions. For example, wells (points), streams (lines), and lakes (polygons). The SubtypeGroupLayer provides the functionality to treat them as one layer called Water Features even though they are stored as separate feature layers.\n\nSee {@link https://developers.arcgis.com/web-map-specification/objects/subtypeGroupLayer/}.",
             "properties": {
                 "blendMode": {
                     "description": "Blend modes are used to blend layers together to create an interesting effect in a layer, or even to produce what seems like a new layer.",

package/messaging/schema/web-action.schema.json

@@ -1473,6 +1473,65 @@
             ],
             "type": "string"
         },
+        "ChooseLayersOptions": {
+            "additionalProperties": false,
+            "description": "Arguments for the \"portal.choose-layers\" operation.",
+            "properties": {
+                "allowMultiple": {
+                    "description": "Whether the user can choose multiple layers, or just one. Default is `false`.",
+                    "type": "boolean"
+                },
+                "attributes": {
+                    "description": "Optional layout XML attributes to be used for the transient UI container."
+                },
+                "icon": {
+                    "description": "Optional icon that may be used by the transient UI container.",
+                    "type": "string"
+                },
+                "initialSource": {
+                    "$ref": "#/definitions/Source",
+                    "description": "Optionally specify the source that will be initially selected. If specified this will overwrite the configured default in the Portal Model."
+                },
+                "layerFilterTags": {
+                    "description": "Optionally specify the tags by which the Choose Layer modal will filter out the displayed layers. If specified this will overwrite the configured default in the Portal Model.",
+                    "items": {
+                        "type": "string"
+                    },
+                    "type": "array"
+                },
+                "maps": {
+                    "$ref": "MapsLike",
+                    "description": "Map(s) to use for the command/operation."
+                },
+                "parent": {
+                    "description": "The layout ID or ItemRef to target for the command/operation. This component will be the parent of the temporary UI that will be removed after the command/operation completes.",
+                    "type": "string"
+                },
+                "sources": {
+                    "description": "Optionally specify the sources that we want to expose. If specified this will overwrite the configured default in the Portal Model.",
+                    "items": {
+                        "$ref": "#/definitions/Source"
+                    },
+                    "type": "array"
+                }
+            },
+            "type": "object"
+        },
+        "ChooseLayersResult": {
+            "additionalProperties": false,
+            "description": "Result of the \"portal.choose-layers\" operation.",
+            "properties": {
+                "layers": {
+                    "$ref": "#/definitions/LayersLike",
+                    "description": "The layer(s) chosen by the user."
+                },
+                "maps": {
+                    "$ref": "MapsLike",
+                    "description": "Map(s) to use for the command/operation."
+                }
+            },
+            "type": "object"
+        },
         "ClearMarkupArgs": {
             "additionalProperties": false,
             "description": "Arguments for the \"map.clear-markup\" command.",
@@ -1889,6 +1948,40 @@
             ],
             "type": "object"
         },
+        "CreateOrUpdateItemArgs": {
+            "additionalProperties": false,
+            "description": "Arguments for the 'portal.create-or-update-item' operation.",
+            "properties": {
+                "data": {
+                    "description": "The JSON data associated with the item."
+                },
+                "promptForOverwrite": {
+                    "description": "Whether to prompt before overwriting an existing item. This must be set to `false` to allow overwriting if `showUI` is also `false`. Defaults to `true`.",
+                    "type": "boolean"
+                },
+                "showUI": {
+                    "description": "Whether to show UI elements associated with this operation. Defaults to `true`.",
+                    "type": "boolean"
+                },
+                "thumbnail": {
+                    "description": "The URL of a thumbnail for the item.",
+                    "type": "string"
+                },
+                "title": {
+                    "description": "The title of the resulting portal item. Must be provided if `showUI` is `false`.",
+                    "type": "string"
+                },
+                "type": {
+                    "description": "The portal type of the item.",
+                    "type": "string"
+                }
+            },
+            "required": [
+                "data",
+                "type"
+            ],
+            "type": "object"
+        },
         "DeleteAttachmentArgs": {
             "additionalProperties": false,
             "description": "Arguments for the \"edit.delete-attachment\" command.",
@@ -6954,6 +7047,17 @@
             },
             "type": "object"
         },
+        "Source": {
+            "description": "Represent sources of portal items.",
+            "enum": [
+                "my-content",
+                "my-favorites",
+                "my-groups",
+                "organization",
+                "public"
+            ],
+            "type": "string"
+        },
         "StopGeometryEditArgs": {
             "additionalProperties": false,
             "description": "Arguments for the \"sketching.stop\" operation.",
@@ -16069,7 +16173,7 @@
         },
         "esri.rest-api.SubtypeGroupLayerJson.SubtypeGroupLayerJson": {
             "additionalProperties": false,
-            "description": "SubtypeGroupLayer provides the ability to organize several sublayers into one common layer. Suppose there are several FeatureLayers that all represent water features in different dimensions. For example, wells (points), streams (lines), and lakes (polygons). The SubtypeGroupLayer provides the functionality to treat them as one layer called Water Features even though they are stored as separate feature layers.\n\nSee {@link https://developers.arcgis.com/web-scene-specification/objects/subtypeGroupLayer/}.",
+            "description": "SubtypeGroupLayer provides the ability to organize several sublayers into one common layer. Suppose there are several FeatureLayers that all represent water features in different dimensions. For example, wells (points), streams (lines), and lakes (polygons). The SubtypeGroupLayer provides the functionality to treat them as one layer called Water Features even though they are stored as separate feature layers.\n\nSee {@link https://developers.arcgis.com/web-map-specification/objects/subtypeGroupLayer/}.",
             "properties": {
                 "blendMode": {
                     "description": "Blend modes are used to blend layers together to create an interesting effect in a layer, or even to produce what seems like a new layer.",
@@ -20849,6 +20953,30 @@
                 }
             ]
         },
+        "portal.choose-layers": {
+            "description": "Allows the user to browse/search the application's associated portal for one or more layers. Web only.",
+            "enum": [
+                "portal.choose-layers"
+            ]
+        },
+        "portal.choose-layers:input": {
+            "$ref": "#/definitions/ChooseLayersOptions"
+        },
+        "portal.choose-layers:output": {
+            "$ref": "#/definitions/ChooseLayersResult"
+        },
+        "portal.create-or-update-item": {
+            "description": "Creates or updates a portal item from the supplied data. Web only.",
+            "enum": [
+                "portal.create-or-update-item"
+            ]
+        },
+        "portal.create-or-update-item:input": {
+            "$ref": "#/definitions/CreateOrUpdateItemArgs"
+        },
+        "portal.create-or-update-item:output": {
+            "$ref": "#/definitions/esri.PortalItem"
+        },
         "printing.run": {
             "description": "Run a print job with a given map and template/layout.",
             "enum": [
@@ -26325,6 +26453,38 @@
                     ],
                     "type": "object"
                 },
+                {
+                    "additionalProperties": false,
+                    "properties": {
+                        "arguments": {
+                            "$ref": "#/definitions/portal.choose-layers:input"
+                        },
+                        "name": {
+                            "$ref": "#/definitions/portal.choose-layers"
+                        }
+                    },
+                    "required": [
+                        "name",
+                        "arguments"
+                    ],
+                    "type": "object"
+                },
+                {
+                    "additionalProperties": false,
+                    "properties": {
+                        "arguments": {
+                            "$ref": "#/definitions/portal.create-or-update-item:input"
+                        },
+                        "name": {
+                            "$ref": "#/definitions/portal.create-or-update-item"
+                        }
+                    },
+                    "required": [
+                        "name",
+                        "arguments"
+                    ],
+                    "type": "object"
+                },
                 {
                     "additionalProperties": false,
                     "properties": {
@@ -27237,6 +27397,12 @@
                 {
                     "$ref": "#/definitions/messaging.mix-in-args"
                 },
+                {
+                    "$ref": "#/definitions/portal.choose-layers"
+                },
+                {
+                    "$ref": "#/definitions/portal.create-or-update-item"
+                },
                 {
                     "$ref": "#/definitions/project.create"
                 },

package/messaging/schema/web-event.schema.json

@@ -8214,7 +8214,7 @@
         },
         "esri.rest-api.SubtypeGroupLayerJson.SubtypeGroupLayerJson": {
             "additionalProperties": false,
-            "description": "SubtypeGroupLayer provides the ability to organize several sublayers into one common layer. Suppose there are several FeatureLayers that all represent water features in different dimensions. For example, wells (points), streams (lines), and lakes (polygons). The SubtypeGroupLayer provides the functionality to treat them as one layer called Water Features even though they are stored as separate feature layers.\n\nSee {@link https://developers.arcgis.com/web-scene-specification/objects/subtypeGroupLayer/}.",
+            "description": "SubtypeGroupLayer provides the ability to organize several sublayers into one common layer. Suppose there are several FeatureLayers that all represent water features in different dimensions. For example, wells (points), streams (lines), and lakes (polygons). The SubtypeGroupLayer provides the functionality to treat them as one layer called Water Features even though they are stored as separate feature layers.\n\nSee {@link https://developers.arcgis.com/web-map-specification/objects/subtypeGroupLayer/}.",
             "properties": {
                 "blendMode": {
                     "description": "Blend modes are used to blend layers together to create an interesting effect in a layer, or even to produce what seems like a new layer.",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vertigis/viewer-spec",
-  "version": "57.2.0",
+  "version": "57.4.0",
   "license": "SEE LICENSE IN LICENSE",
   "description": "VertiGIS Viewer Specification",
   "type": "module",
@@ -43,7 +43,8 @@
   ],
   "peerDependencies": {
     "@arcgis/core": "*",
-    "@vertigis/arcgis-extensions": ">= 45.0.0-0 < 46.0.0-0"
+    "highcharts": "*",
+    "@vertigis/arcgis-extensions": ">= 46.0.0-0 < 47.0.0-0"
   },
   "devDependencies": {
     "@prettier/plugin-xml": "3.3.1",
@@ -59,7 +60,6 @@
     "eslint-plugin-no-autofix": "1.2.3",
     "eslint-plugin-only-warn": "1.1.0",
     "glob": "10.3.10",
-    "highcharts": "11.4.0",
     "lint-staged": "15.2.2 ",
     "path-equal": "1.2.5",
     "prettier": "3.2.5",

package/version.d.ts

@@ -1,4 +1,4 @@
 /**
  * The current version of the VertiGIS Studio Viewer Specification.
  */
-export declare const version = "57.2.0";
+export declare const version = "57.4.0";

package/version.js

@@ -1,4 +1,4 @@
 /**
  * The current version of the VertiGIS Studio Viewer Specification.
  */
-export const version = "57.2.0";
+export const version = "57.4.0";