@git.zone/tsdoc 1.1.37 → 1.1.39

package/dist_ts/00_commitinfo_data.js

@@ -3,7 +3,7 @@
  */
 export const commitinfo = {
     name: '@git.zone/tsdoc',
-    version: '1.1.37',
+    version: '1.1.39',
     description: 'An advanced TypeScript documentation tool using AI to generate and enhance documentation for TypeScript projects.'
 };
 //# sourceMappingURL=data:application/json;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoiMDBfY29tbWl0aW5mb19kYXRhLmpzIiwic291cmNlUm9vdCI6IiIsInNvdXJjZXMiOlsiLi4vdHMvMDBfY29tbWl0aW5mb19kYXRhLnRzIl0sIm5hbWVzIjpbXSwibWFwcGluZ3MiOiJBQUFBOztHQUVHO0FBQ0gsTUFBTSxDQUFDLE1BQU0sVUFBVSxHQUFHO0lBQ3hCLElBQUksRUFBRSxpQkFBaUI7SUFDdkIsT0FBTyxFQUFFLFFBQVE7SUFDakIsV0FBVyxFQUFFLG1IQUFtSDtDQUNqSSxDQUFBIn0=

package/dist_ts/aidocs_classes/commit.d.ts

@@ -1,9 +1,9 @@
 import { AiDoc } from '../classes.aidoc.js';
 export interface INextCommitObject {
     recommendedNextVersionLevel: 'fix' | 'feat' | 'BREAKING CHANGE';
-    recommendedScope: string;
+    recommendedNextVersionScope: string;
+    recommendedNextVersionMessage: string;
     recommendedNextVersion: string;
-    message: string;
     changelog?: string;
 }
 export declare class Commit {

package/dist_ts/aidocs_classes/commit.js

@@ -33,9 +33,9 @@ Your answer should be parseable with JSON.parse() without modifying anything.
 Here is the structure of the JSON you should return:
 {
   recommendedNextVersionLevel: 'fix' | 'feat' | 'BREAKING CHANGE'; // the recommended next version level of the project
-  recommendedScope: string; // the recommended scope name of the next version, like "core" or "cli", or specific class names.
-  recommendedNextVersion: string; // the recommended next version of the project
-  message: string; // the commit message. Don't put fix() feat() or BREAKING CHANGE in the message. Please just the message itself.
+  recommendedNextVersionScope: string; // the recommended scope name of the next version, like "core" or "cli", or specific class names.
+  recommendedNextVersionMessage: string; // the commit message. Don't put fix() feat() or BREAKING CHANGE in the message. Please just the message itself.
+  recommendedNextVersion: string; // the recommended next version of the project, x.x.x
 }
 
 You are being given the files of the project. You should use them to create the commit message.
@@ -66,7 +66,7 @@ You are given
 
 Only return the changelog file, so it can be written directly to changelog.md
 
-For the latest version, that is not yet part of the commit messages, use {{nextVersion}} and {{nextDescription}} placeholders.
+For the latest version, that is not yet part of the commit messages, use {{nextVersion}}, {{nextVersionScope}} and {{nextVersionMessage}} placeholders.
       `,
             userMessage: `
 The previous changelog file is:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@git.zone/tsdoc",
-  "version": "1.1.37",
+  "version": "1.1.39",
   "private": false,
   "description": "An advanced TypeScript documentation tool using AI to generate and enhance documentation for TypeScript projects.",
   "type": "module",

package/ts/00_commitinfo_data.ts

@@ -3,6 +3,6 @@
  */
 export const commitinfo = {
   name: '@git.zone/tsdoc',
-  version: '1.1.37',
+  version: '1.1.39',
   description: 'An advanced TypeScript documentation tool using AI to generate and enhance documentation for TypeScript projects.'
 }

package/ts/aidocs_classes/commit.ts

@@ -4,10 +4,10 @@ import { ProjectContext } from './projectcontext.js';
 
 export interface INextCommitObject {
   recommendedNextVersionLevel: 'fix' | 'feat' | 'BREAKING CHANGE'; // the recommended next version level of the project
-  recommendedScope: string; // the recommended scope name of the next version, like "core" or "cli", or specific class names.
-  recommendedNextVersion: string; // the recommended next version of the project
-  message: string; // the commit message. use conventional commits format
-  changelog?: string; // the changelog
+  recommendedNextVersionScope: string; // the recommended scope name of the next version, like "core" or "cli", or specific class names.
+  recommendedNextVersionMessage: string; // the commit message. Don't put fix() feat() or BREAKING CHANGE in the message. Please just the message itself.
+  recommendedNextVersion: string; // the recommended next version of the project, x.x.x
+  changelog?: string; // the changelog for the next version
 }
 
 export class Commit {
@@ -47,9 +47,9 @@ Your answer should be parseable with JSON.parse() without modifying anything.
 Here is the structure of the JSON you should return:
 {
   recommendedNextVersionLevel: 'fix' | 'feat' | 'BREAKING CHANGE'; // the recommended next version level of the project
-  recommendedScope: string; // the recommended scope name of the next version, like "core" or "cli", or specific class names.
-  recommendedNextVersion: string; // the recommended next version of the project
-  message: string; // the commit message. Don't put fix() feat() or BREAKING CHANGE in the message. Please just the message itself.
+  recommendedNextVersionScope: string; // the recommended scope name of the next version, like "core" or "cli", or specific class names.
+  recommendedNextVersionMessage: string; // the commit message. Don't put fix() feat() or BREAKING CHANGE in the message. Please just the message itself.
+  recommendedNextVersion: string; // the recommended next version of the project, x.x.x
 }
 
 You are being given the files of the project. You should use them to create the commit message.
@@ -82,7 +82,7 @@ You are given
 
 Only return the changelog file, so it can be written directly to changelog.md
 
-For the latest version, that is not yet part of the commit messages, use {{nextVersion}} and {{nextDescription}} placeholders.
+For the latest version, that is not yet part of the commit messages, use {{nextVersion}}, {{nextVersionScope}} and {{nextVersionMessage}} placeholders.
       `,
       userMessage: `
 The previous changelog file is: