@promptbook/types 0.68.0-4 → 0.68.0-5

package/esm/typings/src/_packages/types.index.d.ts

@@ -14,6 +14,7 @@ import type { PrettifyOptions } from '../conversion/prettify/PrettifyOptions';
 import type { renderPipelineMermaidOptions } from '../conversion/prettify/renderPipelineMermaidOptions';
 import type { ErrorJson } from '../errors/utils/ErrorJson';
 import type { AvailableModel } from '../execution/AvailableModel';
+import type { CommonExecutionToolsOptions } from '../execution/CommonExecutionToolsOptions';
 import type { EmbeddingVector } from '../execution/EmbeddingVector';
 import type { ExecutionTools } from '../execution/ExecutionTools';
 import type { LlmExecutionTools } from '../execution/LlmExecutionTools';
@@ -238,6 +239,7 @@ export type { PrettifyOptions };
 export type { renderPipelineMermaidOptions };
 export type { ErrorJson };
 export type { AvailableModel };
+export type { CommonExecutionToolsOptions };
 export type { EmbeddingVector };
 export type { ExecutionTools };
 export type { LlmExecutionTools };

package/esm/typings/src/commands/TEMPLATE/templateCommandParser.d.ts

@@ -8,5 +8,13 @@ import type { TemplateCommand } from './TemplateCommand';
  */
 export declare const templateCommandParser: PipelineTemplateCommandParser<TemplateCommand>;
 /**
- * Note: [⛱] There are two types of KNOWLEDGE, ACTION and INSTRUMENT commands @@@!!!!!!
+ * Note: [⛱] There are two types of KNOWLEDGE, ACTION and INSTRUMENT commands:
+ * 1) There are commands `KNOWLEDGE`, `ACTION` and `INSTRUMENT` used in the pipeline head, they just define the knowledge, action or instrument as single line after the command
+ *    - KNOWLEDGE Look at https://en.wikipedia.org/wiki/Artificial_intelligence
+ * 2) `KNOWLEDGE TEMPLATE` which has short form `KNOWLEDGE` is used in the template, does not refer the line itself, but the content of the template
+ *   - KNOWLEDGE TEMPLATE
+ *
+ *   ```
+ *   Look at https://en.wikipedia.org/wiki/Artificial_intelligence
+ *   ```
  */

package/esm/typings/src/commands/_BOILERPLATE/boilerplateCommandParser.d.ts

@@ -9,6 +9,3 @@ import type { BoilerplateCommand } from './BoilerplateCommand';
  * @private within the commands folder
  */
 export declare const boilerplateCommandParser: PipelineBothCommandParser<BoilerplateCommand>;
-/**
- * TODO: !!!!!! Make .ptbk.md file with examples of the BOILERPLATE command and fail
- */

package/esm/typings/src/execution/CommonExecutionToolsOptions.d.ts

@@ -1,7 +1,7 @@
 /**
  * @@@
  *
- * @private just abstract the common properties for the execution tools
+ * Note: Keep it public to allow people to make their own execution tools
  */
 export type CommonExecutionToolsOptions = {
     /**

package/esm/typings/src/types/PipelineJson/PipelineJson.d.ts

@@ -86,6 +86,7 @@ export type PipelineJson = {
     readonly preparations: Array<PreparationJson>;
 };
 /**
+ * TODO: [🛳] Default PERSONA for the pipeline `defaultPersonaName` (same as `defaultModelRequirements`)
  * TODO: [🍙] Make some standard order of json properties
  * TODO: [🧠] Maybe wrap all {parameterNames} in brackets for example { "resultingParameterName": "{foo}" }
  * Note: [💼] There was a proposal for multiple types of promptbook objects 78816ff33e2705ee1a187aa2eb8affd976d4ea1a

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@promptbook/types",
-    "version": "0.68.0-4",
+    "version": "0.68.0-5",
     "description": "Supercharge your use of large language models",
     "private": false,
     "sideEffects": false,
@@ -45,6 +45,6 @@
     ],
     "typings": "./esm/typings/src/_packages/types.index.d.ts",
     "peerDependencies": {
-        "@promptbook/core": "0.68.0-4"
+        "@promptbook/core": "0.68.0-5"
     }
 }