14.07

.gitignore

@@ -14,3 +14,7 @@ projects/$2sxc/docs/obj
 
 # Sub-Projects dist - to make sure results don't appear in search
 projects/quick-dialog/dist
+
+projects/sxc-typings/parts/dist
+
+projects/sxc-docs

package.json

@@ -1,6 +1,6 @@
 {
   "name": "2sxc-ui",
-  "version": "14.03.00",
+  "version": "14.07.00",
   "description": "2sxc UI - the JS UI of 2sxc",
   "scripts": {
     "release-all": "npm run js2sxc && npm run inpage && npm run snippets && npm run quickdialog && npm run turn-on",

projects/$2sxc/package.json

@@ -25,7 +25,7 @@
     "ts-loader": "^7.0.0",
     "type2docfx": "^0.10.5",
     "typedoc": "^0.15.8",
-    "typescript": "^3.8.3",
+    "typescript": "^4.7.4",
     "webpack": "^4.42.1",
     "webpack-cli": "^3.3.11",
     "webpack-shell-plugin": "^0.5.0"

projects/$2sxc/src/_/Window.ts

@@ -2,6 +2,7 @@ import { SxcGlobal } from '../sxc-global';
 
 /**
  * export interface WindowInternal extends
+ * @public
  */
 declare global {
     interface Window {
@@ -11,7 +12,7 @@ declare global {
         $2sxc: SxcGlobal;
 
         /** @internal */
-        $: JQueryStatic & DnnJQueryExtensions;
+        $: any & DnnJQueryExtensions;
     }
 }
 

projects/$2sxc/src/cms/command-names.ts

@@ -9,13 +9,15 @@
 
 /**
  * Names of commands known to 2sxc CMS - for use in toolbars and calling commands directly from code
+ * @public
  */
 export enum CommandNames {
     /**
-     * `add` opens a `new` dialog to create and add a new item to a **list of items**.
+     * `add` adds another demo-item to a **list of items**.
+     * It does not open the edit-dialog.
      * <br> The new item is placed after the item the (+) was clicked on.
      * <br>💡
-     * This is similar to `new` but also adds the item to the existing list of items shown on the page.
+     * This is different than new, which opens a dialog to add something. 
      * <br> 🪜 Only appears on toolbars of items which are in a list.
      * <br> 📩 [Parameters](xref:Api.Js.SxcJs.CommandAddParams)
      */
@@ -73,20 +75,33 @@ export enum CommandNames {
     apps = 'apps',
 
     /**
-     * `contentitems` opens the list to manage all items of a specific content-type.
+     * `data` opens the list to manage all items of a specific content-type.
      * <br> 🔘 Will use the settings of the current template to open.
      * It is only shown to elevated admins.
-     * <br> 📩 [Parameters](xref:Api.Js.SxcJs.CommandContentItemsParams)
+     * <br> 📩 [Parameters](xref:Api.Js.SxcJs.CommandDataParams)
      */
-    contentItems = 'contentitems',
+    data = 'data',
 
     /**
-     * `contenttype` opens the dialog to view or modify fields of a content-type.
+     * old name
+     * @internal
+     */
+    data_old_contentItems = 'contentitems',
+
+    /**
+     * `fields` opens the dialog to view or modify fields of a content-type.
      * <br> 🔘 On a toolbar it will use the content-type of the current item.
      * <br> 🔐 Toolbar shows this automatically to elevated admins.
      * <br> 📩 [Parameters](xref:Api.Js.SxcJs.CommandContentTypeParams)
      */
-    contentType = 'contenttype',
+    fields = 'fields',
+
+    /**
+     * old name
+     * @internal
+     */
+    fields_old_contenttype = 'contenttype',
+
 
     /**
      * `copy` opens the edit-dialog for the current item in copy-mode, so when saving it will be a new item.
@@ -96,11 +111,17 @@ export enum CommandNames {
     copy = 'copy',
 
     /**
-     * `custom` will execute custom javascript.
+     * `code` will execute custom javascript.
      * <br> 🔘 This is mainly for toolbars, to add buttons with custom code.
-     * <br> 📩 [Parameters](xref:Api.Js.SxcJs.CommandCustomParams)
+     * <br> 📩 [Parameters](xref:Api.Js.SxcJs.CommandCodeParams)
+     */
+    code = 'code',
+
+    /**
+     * old name
+     * @internal
      */
-    custom = 'custom',
+    code_old_custom = 'custom',
 
     /**
      * `delete` will delete (not just remove) a content-item.
@@ -114,7 +135,8 @@ export enum CommandNames {
     /**
      * `edit` opens an edit-dialog.
      * <br>
-     * In scenarios where the page is currently showing a demo item, this will have the same effect as `add`
+     * In scenarios where the page is currently showing a _demo item_, this will have the same effect as `add`.
+     * So instead of editing the _demo item_ it would trigger a dialog to add a new item. 
      * <br> 🔘 Only appears if `entityId` is known or item is in a list.
      * <br> 📩 Parameters either one of these: 
      * [Id](xref:Api.Js.SxcJs.CommandParamsEntityById),
@@ -131,19 +153,32 @@ export enum CommandNames {
     image = 'image',
 
     /**
-     * `insights-server` opens the insights logs page
+     * `insights` opens the insights logs page
      * <br> 🔐 Toolbar shows this automatically to elevated admins.
      * <br> 📩 No params required.
      */
-    insightsServer = 'insights-server',
+    insights = 'insights',
+
+    /**
+     * old name
+     * @internal
+     */
+    insights_old_server = 'insights-server',
 
     /**
      * `instance-list` opens a dialog to manually re-order **items in a list**.
      * <br> 🪜 Only appears on toolbars of items which are in a list.
      * <br> 📩 No params required,
      * (auto-detected from context)
      */
-    instanceList = 'instance-list',
+    list = 'list',
+
+    /**
+     * old name
+     * @internal
+     */
+    list_old_instanceList = 'instance-list',
+
 
     /**
      * `layout` opens the in-page dialog to change the layout of the current content.
@@ -188,12 +223,13 @@ export enum CommandNames {
     moveUp = 'moveup',
 
     /**
-     * `new` opens the edit-dialog for a new content-item.
+     * `new` opens the edit-dialog to create a new item/entity.
      * <br>
-     * It will only create an item, not add it to a list. 
-     * For that you would need to use `add`
-     * <br> 📩 [Parameters](xref:Api.Js.SxcJs.CommandContentTypeParams)
-     * (auto-detected from context)
+     * If the previous item is in a list, it will add it to that list _after_ the previous item with the toolbar. 
+     * Otherwise it just creates it and the visualization will differ depending on the App.
+     * <br> 🪜 It works differently for lists - in which case it also adds it to the list. 
+     * <br> 📩 [Parameters](xref:Api.Js.SxcJs.CommandNewParams)
+     * (usually auto-detected from context)
      */
     new = 'new',
 
@@ -235,7 +271,14 @@ export enum CommandNames {
      * <br> 📩 No params required,
      * (auto-detected from context)
      */
-    templateDevelop = 'template-develop',
+    template = 'template',
+
+    /**
+     * old name
+     * @internal
+     */
+    template_old_develop = 'template-develop',
+
 
     /**
      * `template-query` opens the pipeline/query-designer in a new window.
@@ -245,21 +288,39 @@ export enum CommandNames {
      * <br> 📩 No params required,
      * (auto-detected from context)
      */
-    templateQuery = 'template-query',
+    query = 'query',
 
+    /**
+     * old name
+     * @internal
+     */
+    query_old_templateQuery = 'template-query',
+
     /**
      * `template-settings` will change settings on the template currently used
      * <br> 🔐 Toolbar shows this automatically to elevated admins.
      */
-    templateSettings = 'template-settings',
+    view = 'view',
+
+    /**
+     * old name
+     * @internal
+     */
+    view_old_templateSettings = 'template-settings',
 
     /**
-     * `zone` opens the system dialog for this zone/site.
+     * `system` opens the system dialog for this zone/site.
      * <br> 🔐 Toolbar shows this automatically to elevated admins.
      * <br> 📩 No params required,
      * (auto-detected from context)
      */
-    zone = 'zone',
+    system = 'system',
+
+    /**
+     * old name
+     * @internal
+     */
+    system_old_zone = 'zone',
 }
 
 

projects/$2sxc/src/cms/command-params-metadata.ts

@@ -2,6 +2,7 @@ import { MetadataTargetTypes } from '../data';
 
 /**
  * Parameters on `metadata` for commands which have a metadata-target. 
+ * @public
  */
 export interface CommandParamsMetadata {
     /**