@isardsat/editorial-cli 6.15.0 → 6.17.0

package/dist/commands/init.js

@@ -1,70 +1,25 @@
 import { Command } from "@commander-js/extra-typings";
-import { existsSync } from "node:fs";
-import { mkdir, writeFile } from "node:fs/promises";
+import { mkdir } from "node:fs/promises";
 import * as path from "node:path";
+import { configData, dataJson, schemaData, } from "../constants/editorialFiles.js";
+import { createFileIfNotExists } from "../lib/files.js";
 export const initCommand = new Command()
     .name("init")
-    .description("initialize files required for Editorial to function")
+    .description("Initialize files required for Editorial to function")
     .action(async () => {
     console.log("Initializing editorial...");
-    // Check if the editorial directory already exists
-    if (existsSync("./editorial")) {
-        console.log("Editorial directory already exists!");
-        return process.exit(1);
-    }
     try {
         await mkdir("./editorial", { recursive: true });
         console.log("Created Editorial directory");
-        // Create config.json with basic configuration
-        const configData = JSON.stringify({
-            name: "Editorial",
-            publicUrl: "http://localhost:3001/",
-            previewUrl: "http://localhost:3001/preview/",
-        }, null, 2);
-        await writeFile(path.join("editorial", "config.json"), configData);
-        console.log("Created config.json");
-        // Create schema.yaml with a dummy schema
-        const schemaData = `
-      # ----------------------------------- Editorial Meta Schema YAML File ------------------------------------
-      # If you are using an editor that supports JSON Schema, you can use the following URL
-      # to get validation and autocompletion based on the Editorial meta-schema.
-      # For example, VSCode with redhat.vscode-yaml extension should work out of the box.
-      # Make sure to replace "localhost:3001" with the actual address of your Editorial if it's different.
-      # allowedExtraFields parameter can be used to allow additional fields in the schema that are not defined in the meta-schema.
-      # Don't uncomment the yaml-language-server line below, it is required for the editor to recognize the schema.
-      #----------------------------------------------------------------------------------------------------------
-          
-      # yaml-language-server: $schema=http://localhost:3001/api/v1/meta-schema
-
-      
-      # Editorial Schema
-dummy:
-  displayName: Dummy Object
-  fields:
-    title:
-      type: string
-      displayName: Title
-      showInSummary: true
-    body:
-      type: markdown
-      displayName: Body
-      displayExtra: "Write anything you want!"
-`;
-        await writeFile(path.join("editorial", "schema.yaml"), schemaData);
-        console.log("Created schema.yaml");
-        // Create data.json with test object
-        const dataJson = JSON.stringify({
-            dummy: {
-                "test-1": {
-                    id: "test-1",
-                    title: "Test Object",
-                    body: "This is a **test** object",
-                },
-            },
-        }, null, 2);
-        await writeFile(path.join("editorial", "data.json"), dataJson);
-        console.log("Created data.json");
-        await mkdir(path.join("public"), { recursive: true });
+        const files = [
+            { path: "editorial/config.json", content: configData },
+            { path: "editorial/schema.yaml", content: schemaData },
+            { path: "editorial/data.json", content: dataJson },
+        ];
+        for (const file of files) {
+            await createFileIfNotExists(file.path, file.content);
+        }
+        await mkdir(path.join("public", "editorialFiles"), { recursive: true });
         console.log("Created files directory");
         console.log("Editorial initialized successfully!");
     }

package/dist/constants/editorialFiles.d.ts

@@ -0,0 +1,3 @@
+export declare const configData: string;
+export declare const schemaData = "\n# ----------------------------------- Editorial Meta Schema YAML File ------------------------------------\n# If you are using an editor that supports JSON Schema, you can use the following URL\n# to get validation and autocompletion based on the Editorial meta-schema.\n# For example, VSCode with redhat.vscode-yaml extension should work out of the box.\n# Make sure to replace \"localhost:3001\" with the actual address of your Editorial if it's different.\n# allowedExtraFields parameter can be used to allow additional fields in the schema that are not defined in the meta-schema.\n# Don't uncomment the yaml-language-server line below, it is required for the editor to recognize the schema.\n#----------------------------------------------------------------------------------------------------------\n\n# yaml-language-server: $schema=http://localhost:3001/api/v1/meta-schema\n\n# Editorial Schema\ndummy:\n  displayName: Dummy Object\n  fields:\ntitle:\n  type: string\n  displayName: Title\n  showInSummary: true\nbody:\n  type: markdown\n  displayName: Body\n  displayExtra: \"Write anything you want!\"\n";
+export declare const dataJson: string;

package/dist/constants/editorialFiles.js

@@ -0,0 +1,52 @@
+export const configData = JSON.stringify({
+    name: "Editorial",
+    publicUrl: "http://localhost:3001/",
+    previewUrl: "http://localhost:3001/preview/",
+    publicDir: "public/editorialFiles",
+    filesUrl: "",
+    largeFilesUrl: "",
+    firebase: {
+        apiKey: "",
+        authDomain: "",
+        databaseURL: "",
+        projectId: "",
+        storageBucket: "",
+        messagingSenderId: "",
+        appId: "",
+        dbUsersPath: "",
+    },
+}, null, 2);
+export const schemaData = `
+# ----------------------------------- Editorial Meta Schema YAML File ------------------------------------
+# If you are using an editor that supports JSON Schema, you can use the following URL
+# to get validation and autocompletion based on the Editorial meta-schema.
+# For example, VSCode with redhat.vscode-yaml extension should work out of the box.
+# Make sure to replace "localhost:3001" with the actual address of your Editorial if it's different.
+# allowedExtraFields parameter can be used to allow additional fields in the schema that are not defined in the meta-schema.
+# Don't uncomment the yaml-language-server line below, it is required for the editor to recognize the schema.
+#----------------------------------------------------------------------------------------------------------
+
+# yaml-language-server: $schema=http://localhost:3001/api/v1/meta-schema
+
+# Editorial Schema
+dummy:
+  displayName: Dummy Object
+  fields:
+title:
+  type: string
+  displayName: Title
+  showInSummary: true
+body:
+  type: markdown
+  displayName: Body
+  displayExtra: "Write anything you want!"
+`;
+export const dataJson = JSON.stringify({
+    dummy: {
+        "test-1": {
+            id: "test-1",
+            title: "Test Object",
+            body: "This is a **test** object",
+        },
+    },
+}, null, 2);

package/dist/lib/files.d.ts

@@ -0,0 +1 @@
+export declare function createFileIfNotExists(filePath: string, content: string): Promise<void>;

package/dist/lib/files.js

@@ -0,0 +1,15 @@
+import { writeFile } from "node:fs/promises";
+export async function createFileIfNotExists(filePath, content) {
+    try {
+        await writeFile(filePath, content, { flag: "wx" });
+        console.log(`Created ${filePath}`);
+    }
+    catch (err) {
+        if (err.code === "EEXIST") {
+            console.log(`${filePath} already exists, skipping`);
+        }
+        else {
+            throw err;
+        }
+    }
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@isardsat/editorial-cli",
-  "version": "6.15.0",
+  "version": "6.17.0",
   "type": "module",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",
@@ -14,7 +14,7 @@
     "@commander-js/extra-typings": "^13.0.0",
     "@hono/node-server": "^1.13.8",
     "commander": "^13.1.0",
-    "@isardsat/editorial-server": "^6.15.0"
+    "@isardsat/editorial-server": "^6.17.0"
   },
   "devDependencies": {
     "@tsconfig/node22": "^22.0.0",