@dosgato/templating 0.0.51 → 0.0.52

package/dist/apitemplate.d.ts

@@ -107,7 +107,7 @@ export interface APIComponentTemplate extends APITemplate {
      *
      * See the ComponentExtras type to see all the contextual information you'll have available.
      */
-    validate?: (data: ComponentData, extras: ComponentExtras) => Promise<ValidationFeedback[]>;
+    validate?: <T extends ComponentData>(data: T, extras: ComponentExtras) => Promise<ValidationFeedback[]>;
     /**
      * Each template must provide a list of migrations for upgrading the data schema over time.
      * Typically this will start as an empty array and migrations will be added as the template
@@ -124,7 +124,7 @@ export interface APIPageTemplate extends APITemplate {
     /**
      * Page template implementations do not receive a path like component templates do.
      */
-    validate?: (data: PageData, extras: PageExtras) => Promise<ValidationFeedback[]>;
+    validate?: <T extends PageData>(data: T, extras: PageExtras) => Promise<ValidationFeedback[]>;
     migrations?: PageMigration[];
     /**
      * Hard-coded properties that may be set on page templates to influence the rendering of
@@ -144,7 +144,7 @@ export interface APIDataTemplate extends APITemplate {
      * as well as the folder id (if applicable) and their own id. Keep in mind dataId will be
      * null when it is a creation operation.
      */
-    validate?: (data: ComponentData, extras: DataExtras) => Promise<ValidationFeedback[]>;
+    validate?: <T extends DataData>(data: T, extras: DataExtras) => Promise<ValidationFeedback[]>;
     migrations?: DataMigration[];
 }
 export declare type APIAnyTemplate = APIComponentTemplate | APIPageTemplate | APIDataTemplate;

package/package.json

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