@git.zone/tsdoc 1.1.37 → 1.1.38

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -3,7 +3,7 @@
3
3
  */
4
4
  export const commitinfo = {
5
5
  name: '@git.zone/tsdoc',
6
- version: '1.1.37',
6
+ version: '1.1.38',
7
7
  description: 'An advanced TypeScript documentation tool using AI to generate and enhance documentation for TypeScript projects.'
8
8
  };
9
9
  //# sourceMappingURL=data:application/json;base64,eyJ2ZXJzaW9uIjozLCJmaWxlIjoiMDBfY29tbWl0aW5mb19kYXRhLmpzIiwic291cmNlUm9vdCI6IiIsInNvdXJjZXMiOlsiLi4vdHMvMDBfY29tbWl0aW5mb19kYXRhLnRzIl0sIm5hbWVzIjpbXSwibWFwcGluZ3MiOiJBQUFBOztHQUVHO0FBQ0gsTUFBTSxDQUFDLE1BQU0sVUFBVSxHQUFHO0lBQ3hCLElBQUksRUFBRSxpQkFBaUI7SUFDdkIsT0FBTyxFQUFFLFFBQVE7SUFDakIsV0FBVyxFQUFFLG1IQUFtSDtDQUNqSSxDQUFBIn0=
@@ -1,9 +1,9 @@
1
1
  import { AiDoc } from '../classes.aidoc.js';
2
2
  export interface INextCommitObject {
3
3
  recommendedNextVersionLevel: 'fix' | 'feat' | 'BREAKING CHANGE';
4
- recommendedScope: string;
4
+ recommendedNextVersionScope: string;
5
+ recommendedNextVersionMessage: string;
5
6
  recommendedNextVersion: string;
6
- message: string;
7
7
  changelog?: string;
8
8
  }
9
9
  export declare class Commit {
@@ -33,9 +33,9 @@ Your answer should be parseable with JSON.parse() without modifying anything.
33
33
  Here is the structure of the JSON you should return:
34
34
  {
35
35
  recommendedNextVersionLevel: 'fix' | 'feat' | 'BREAKING CHANGE'; // the recommended next version level of the project
36
- recommendedScope: string; // the recommended scope name of the next version, like "core" or "cli", or specific class names.
37
- recommendedNextVersion: string; // the recommended next version of the project
38
- message: string; // the commit message. Don't put fix() feat() or BREAKING CHANGE in the message. Please just the message itself.
36
+ recommendedNextVersionScope: string; // the recommended scope name of the next version, like "core" or "cli", or specific class names.
37
+ recommendedNextVersionMessage: string; // the commit message. Don't put fix() feat() or BREAKING CHANGE in the message. Please just the message itself.
38
+ recommendedNextVersion: string; // the recommended next version of the project, x.x.x
39
39
  }
40
40
 
41
41
  You are being given the files of the project. You should use them to create the commit message.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@git.zone/tsdoc",
3
- "version": "1.1.37",
3
+ "version": "1.1.38",
4
4
  "private": false,
5
5
  "description": "An advanced TypeScript documentation tool using AI to generate and enhance documentation for TypeScript projects.",
6
6
  "type": "module",
@@ -3,6 +3,6 @@
3
3
  */
4
4
  export const commitinfo = {
5
5
  name: '@git.zone/tsdoc',
6
- version: '1.1.37',
6
+ version: '1.1.38',
7
7
  description: 'An advanced TypeScript documentation tool using AI to generate and enhance documentation for TypeScript projects.'
8
8
  }
@@ -4,10 +4,10 @@ import { ProjectContext } from './projectcontext.js';
4
4
 
5
5
  export interface INextCommitObject {
6
6
  recommendedNextVersionLevel: 'fix' | 'feat' | 'BREAKING CHANGE'; // the recommended next version level of the project
7
- recommendedScope: string; // the recommended scope name of the next version, like "core" or "cli", or specific class names.
8
- recommendedNextVersion: string; // the recommended next version of the project
9
- message: string; // the commit message. use conventional commits format
10
- changelog?: string; // the changelog
7
+ recommendedNextVersionScope: string; // the recommended scope name of the next version, like "core" or "cli", or specific class names.
8
+ recommendedNextVersionMessage: string; // the commit message. Don't put fix() feat() or BREAKING CHANGE in the message. Please just the message itself.
9
+ recommendedNextVersion: string; // the recommended next version of the project, x.x.x
10
+ changelog?: string; // the changelog for the next version
11
11
  }
12
12
 
13
13
  export class Commit {
@@ -47,9 +47,9 @@ Your answer should be parseable with JSON.parse() without modifying anything.
47
47
  Here is the structure of the JSON you should return:
48
48
  {
49
49
  recommendedNextVersionLevel: 'fix' | 'feat' | 'BREAKING CHANGE'; // the recommended next version level of the project
50
- recommendedScope: string; // the recommended scope name of the next version, like "core" or "cli", or specific class names.
51
- recommendedNextVersion: string; // the recommended next version of the project
52
- message: string; // the commit message. Don't put fix() feat() or BREAKING CHANGE in the message. Please just the message itself.
50
+ recommendedNextVersionScope: string; // the recommended scope name of the next version, like "core" or "cli", or specific class names.
51
+ recommendedNextVersionMessage: string; // the commit message. Don't put fix() feat() or BREAKING CHANGE in the message. Please just the message itself.
52
+ recommendedNextVersion: string; // the recommended next version of the project, x.x.x
53
53
  }
54
54
 
55
55
  You are being given the files of the project. You should use them to create the commit message.