@dosgato/templating 0.0.133 → 0.0.135

package/dist/component.d.ts

@@ -373,6 +373,12 @@ export interface DataData {
     savedAtVersion: string;
     [keys: string]: any;
 }
+export interface AssetData<T = any> {
+    shasum: string;
+    uploadedFilename: string;
+    meta: T;
+    [keys: string]: any;
+}
 export interface ContextBase {
     /**
      * For accessibility, every component should consider whether it is creating headers

package/dist/uitemplate.d.ts

@@ -130,6 +130,42 @@ export interface TracingInterface {
     endTransaction?: (name: string, details: any, env?: TracingEnvironment) => void;
     event?: (name: string, details: any, env?: TracingEnvironment) => void;
 }
+export interface BaseEvent {
+    /** The larger UI area the user is interacting with that the event is emitted from.
+     * @example 'ActionPanel', 'PageEditor', 'ComponentDialog' */
+    eventType: string;
+    /** The specific action the user took. Typically the label for the element that emits
+     * the event.
+     * @example 'Add Page', 'Edit Page', 'Preview', 'Cancel Preview' */
+    action: string;
+    /** Additional data points specific to a particular event type's context. These should
+     * be significant enough to understanding the event to merrit adding additional columns
+     * in tools like elastic-search.
+     * @warning This is NOT a catch-all property.
+     * @example { hiddenLabel: action.hiddenLabel } // The aria label for an action element. */
+    additionalProperties?: Record<string, string | undefined>;
+}
+/** Events triggered by user interactions with interface elements in DosGato. This interface
+ * is intended to provide a common model for succinctly expressing the contextually important
+ * properties of these events to loggers that can be pointed to analytics and metrics services. */
+export interface UserEvent extends BaseEvent {
+    /** The page, screen, or dialog the user is looking at in which the associated event emitter is
+     * in context to.
+     * @example '/pages', '/pages/[id]', '/pages/[id]/dialog' */
+    screen: string;
+    /** The target the emitted event is to trigger actions on.
+     * Each page/screen, or dialog, needs to set their target for what events in it are targeted
+     * to act on in in its context.
+     *
+     * For example: The page in the page tree of the Pages screen that ActionPanel actions,
+     * such as edit or preview, will act on.
+     * @example '/site3-sandbox/about' */
+    target: string;
+}
+interface AssetMetaDisplay {
+    component: UITemplate['dialog'];
+    title: string;
+}
 /**
  * A type for the config object that should be exported from a CMS instance's admin/local/index.js
  * to configure how that instance should work.
@@ -140,7 +176,7 @@ export interface UIConfig {
         /**
          * What to do when we get a 401 from the API. Generally we'll want to redirect
          * to our SSO login page. Since we use sveltekit we redirect by throwing:
-         * `throw redirect(302, 'my.sso.org/login')`
+         * `throw redirect(302, 'https://my.sso.org/login')`
          */
         handleUnauthorized: (environmentConfig: any) => void;
         /**
@@ -180,7 +216,7 @@ export interface UIConfig {
          * If you use cookies or if your SSO provider uses cookies and would immediately log the user back in,
          * then you need to visit a logout endpoint instead of refreshing.
          *
-         * Since we use sveltekit, you trigger navigation with `goto('my.sso.org/logout')`
+         * Since we use sveltekit, you trigger navigation with `goto('https://my.sso.org/logout')`
          */
         logout?: (environmentConfig: any, token: string) => void;
     };
@@ -192,7 +228,31 @@ export interface UIConfig {
      * If you would like to collect more information about assets from editors, you may provide a dialog
      * here. The data collected will be available when you retrieve assets.
      */
-    assetMetaDialog?: UITemplate['dialog'];
+    assetMeta?: {
+        dialog: UITemplate['dialog'];
+        /**
+         * If you provide an assetMeta.dialog to collect extra details about each asset, you'll probably want to
+         * display those details on the asset detail screen. Provide this function to return a map of detail
+         * keys and values to be displayed alongside the other vitals like asset name, size, type, etc. Insertion
+         * order will be maintained.
+         */
+        details?: (data: any) => Record<string, string>;
+        /**
+         * If you provide an assetMeta.dialog to collect extra details about each asset, you may want to use
+         * assetMeta.details to show some of it, and/or you may want your own box on the detail page to do something
+         * cool and custom. Provide a svelte component here and it will be passed the asset object with all of
+         * its metadata so that you can draw whatever you like. Your content will be placed inside a box titled
+         * with the title property.
+         *
+         * Provide an array to be given multiple boxes.
+         */
+        display?: AssetMetaDisplay | AssetMetaDisplay[];
+    };
     tracing?: TracingInterface;
+    /** Non-Awaited async call for logging interface interactions if defined.
+     * Useful for defining how to log form submissions, interaction clicks, page edits, or state
+     * changes of different interfaces. Can be directed to separate endpoint for APM logging as
+     * long as that POST is also non-awaited. */
+    uiInteractionsLogger?: (info: UserEvent, environmentConfig: any) => void;
 }
 export {};

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@dosgato/templating",
-  "version": "0.0.133",
+  "version": "0.0.135",
   "description": "A library to support building templates for dosgato CMS.",
   "type": "module",
   "exports": {