@contentstorage/core 0.3.42 → 0.3.43

package/dist/helpers/setKeyToHtmlTag.d.ts

@@ -0,0 +1 @@
+export declare const setKeyToHtmlTag: (contentKey: string) => void;

package/dist/helpers/setKeyToHtmlTag.js

@@ -0,0 +1,5 @@
+const htmlElem = document.documentElement;
+export const setKeyToHtmlTag = (contentKey) => {
+    const dataKey = `data-contentstorage-key-${contentKey}`;
+    htmlElem.setAttribute(dataKey, 'true');
+};

package/package.json

@@ -2,7 +2,7 @@
   "name": "@contentstorage/core",
   "author": "Kaido Hussar <kaidohus@gmail.com>",
   "homepage": "https://contentstorage.app",
-  "version": "0.3.42",
+  "version": "0.3.43",
   "type": "module",
   "description": "Fetch content from contentstorage and generate TypeScript types",
   "module": "dist/index.js",

package/dist/helpers/defineConfig.d.ts

@@ -1,6 +0,0 @@
-import { AppConfig } from '../types.js';
-/**
- * Helper function to define your application configuration.
- * Provides autocompletion and type-checking for contentstorage.config.js files.
- */
-export declare function defineConfig(config: AppConfig): AppConfig;

package/dist/helpers/defineConfig.js

@@ -1,19 +0,0 @@
-/**
- * Helper function to define your application configuration.
- * Provides autocompletion and type-checking for contentstorage.config.js files.
- */
-export function defineConfig(config) {
-    // You can add basic runtime validation here if desired,
-    // e.g., check if contentUrl is a valid URL format,
-    // or if languageCodes is not empty.
-    if (!config.languageCodes || config.languageCodes.length === 0) {
-        console.warn('Warning: languageCodes array is empty or missing in the configuration.');
-    }
-    if (!config.contentDir) {
-        // This would typically be a hard error, but defineConfig is more for type safety at edit time.
-        // Runtime validation (see point 3) is better for hard errors.
-        console.warn('Warning: contentDir is missing in the configuration.');
-    }
-    // ... other checks
-    return config;
-}