windmill-components 1.472.1 → 1.472.2

package/package/components/copilot/prompts/fixPrompt.d.ts

@@ -0,0 +1,50 @@
+export declare const FIX_PROMPT: {
+    system: string;
+    prompts: {
+        python3: {
+            prompt: string;
+        };
+        deno: {
+            prompt: string;
+        };
+        rust: {
+            prompt: string;
+        };
+        go: {
+            prompt: string;
+        };
+        bash: {
+            prompt: string;
+        };
+        postgresql: {
+            prompt: string;
+        };
+        mysql: {
+            prompt: string;
+        };
+        bigquery: {
+            prompt: string;
+        };
+        snowflake: {
+            prompt: string;
+        };
+        mssql: {
+            prompt: string;
+        };
+        graphql: {
+            prompt: string;
+        };
+        powershell: {
+            prompt: string;
+        };
+        nativets: {
+            prompt: string;
+        };
+        bun: {
+            prompt: string;
+        };
+        php: {
+            prompt: string;
+        };
+    };
+};

package/package/components/copilot/prompts/fixPrompt.js

@@ -0,0 +1,50 @@
+export const FIX_PROMPT = {
+    "system": "You are a helpful coding assistant for Windmill, a developer platform for running scripts. You fix the code shared by the user. Each user message includes some contextual information which should guide your answer.\nOnly output code. Wrap the code in a code block. \nExplain the error and the fix after generating the code inside an <explanation> tag.\nAlso put explanations directly in the code as comments.\nReturn the complete fixed code.\n\nHere's how interactions have to look like:\nuser: {sample_question}\nassistant: ```language\n{code}\n```\n<explanation>{explanation}</explanation>",
+    "prompts": {
+        "python3": {
+            "prompt": "Here's my python3 code: \n```python\n{code}\n```\n<contextual_information>\nYou have to write a function in python called \"main\". Specify the parameter types. Do not call the main function. You should generally return the result.\nThe \"main\" function cannot be async. If you need to use async code, you can use the asyncio library.\nYou can take as parameters resources which are dictionaries containing credentials or configuration information. For Windmill to correctly detect the resources to be passed, the resource type name has to be exactly as specified in the following list:\n<resourceTypes>\n{resourceTypes}\n</resourceTypes>\nYou need to define the type of the resources that are needed before the main function, but only include them if they are actually needed to achieve the function purpose.\nThe resource type name has to be exactly as specified (has to be IN LOEWRCASE). If the type name conflicts with any imported methods, you have to rename the imported method with the conflicting name.\n<contextual_information>\nI get the following error: {error}\nFix my code."
+        },
+        "deno": {
+            "prompt": "Here's my TypeScript code in a deno running environment:\n```typescript\n{code}\n```\n<contextual_information>\nWe have to export a \"main\" function like this: \"export async function main(...)\" and specify the parameter types but do not call it. You should generally return the result.\nIf needed, the standard fetch method is available globally, do not import it.\nYou can take as parameters resources which are dictionaries containing credentials or configuration information. Name the resource parameters like this: \"{resource_type}Resource\".\nThe following resource types are available:\n<resourceTypes>\n{resourceTypes}\n</resourceTypes>\nOnly define the type for resources that are actually needed to achieve the function purpose. The resource type name has to be exactly as specified. If the type name conflicts with the imported object, rename the imported object NOT THE TYPE.\nNaming conventions are guidelines, but follow the user's naming choices in the existing code.\n</contextual_information>\nI get the following error: {error}\nFix my code."
+        },
+        "rust": {
+            "prompt": "Here's my Rust code:\n```rust\n{code}\n```\n<contextual_information>\nPlease define a `main` function in Rust with this signature:\n```rust\npub fn main(...) -> Result<ReturnType, Box<dyn std::error::Error>>\n```\nbut do not call it. Favor idiomatic Rust patterns, ensuring safe handling of ownership and borrowing, robust error handling with `Result`, and concurrency if needed (`async`/`tokio` or std threading). \n\n- Include necessary imports and modules only when needed.\n- Add comments explaining important operations and any unsafe usage (if absolutely required).\n- The generated code should be easily executable and testable in an integrated terminal.\n</contextual_information>\nI get the following error: {error}\nFix my code."
+        },
+        "go": {
+            "prompt": "Here's my go code: \n```go\n{code}\n```\n<contextual_information>\nWe have to export a \"main\" function. Import the packages you need. The return type of the function has to be ({return_type}, error). The file package has to be \"inner\"\n</contextual_information>\nI get the following error: {error}\nFix my code."
+        },
+        "bash": {
+            "prompt": "Here's my bash code: \n```shell\n{code}\n```\n<contextual_information>\nDo not include \"#!/bin/bash\". Arguments are always string and can only be obtained with \"var1=\"$1\"\", \"var2=\"$2\"\", etc... You do not need to check if the arguments are present.\n</contextual_information>\nI get the following error: {error}\nFix my code."
+        },
+        "postgresql": {
+            "prompt": "Here's my PostgreSQL code: \n```sql\n{code}\n```\n<contextual_information>\nArguments can be obtained directly in the statement with `$1::{type}`, `$2::{type}`, etc... Name the parameters (without specifying the type) by adding comments before the statement like that: `-- $1 name1` or `-- $2 name = default` (one per row)\n</contextual_information>\nI get the following error: {error}\nFix my code."
+        },
+        "mysql": {
+            "prompt": "Here's my MySQL code: \n```sql\n{code}\n```\n<contextual_information>\nArguments can be obtained directly in the statement with ?. Name the parameters by adding comments before the statement like that: `-- ? name1 ({type})` or `-- ? name2 ({type}) = default` (one per row)\n</contextual_information>\nI get the following error: {error}\nFix my code."
+        },
+        "bigquery": {
+            "prompt": "Here's my BigQuery code: \n```sql\n{code}\n```\n<contextual_information>\nYou can define arguments by adding comments before the statement like that: `-- @name1 ({type})` or `-- @name2 ({type}) = default` (one per row). They can then be obtained directly in the statement with `@name1`, `@name2`, etc....\n</contextual_information>\nI get the following error: {error}\nFix my code."
+        },
+        "snowflake": {
+            "prompt": "Here's my snowflake code: \n```sql\n{code}\n```\n<contextual_information>\nArguments can be obtained directly in the statement with ?. Name the parameters by adding comments before the statement like that: `-- ? name1 ({type})` or `-- ? name2 ({type}) = default` (one per row)\n</contextual_information>\nI get the following error: {error}\nFix my code."
+        },
+        "mssql": {
+            "prompt": "Here's my Microsoft SQL Server code: \n```sql\n{code}\n```\n<contextual_information>\nArguments can be obtained directly in the statement with @P1, @P2, etc.. Name the parameters by adding comments before the statement like that: `-- @P1 name1 ({type})` or `-- @P2 name2 ({type}) = default` (one per row)\n</contextual_information>\nI get the following error: {error}\nFix my code."
+        },
+        "graphql": {
+            "prompt": "Here's my graphql code: \n```graphql\n{code}\n```\n<contextual_information>\nAdd the needed arguments as query parameters.\n</contextual_information>\nI get the following error: {error}\nFix my code."
+        },
+        "powershell": {
+            "prompt": "Here's my powershell code: \n```powershell\n{code}\n```\n<contextual_information>\nArguments can be obtained by calling the param function on the first line like that: `param($ParamName1, $ParamName2 = \"default value\", [{type}]$ParamName3, ...)`\n</contextual_information>\nI get the following error: {error}\nFix my code."
+        },
+        "nativets": {
+            "prompt": "Here's my TypeScript code: \n```typescript\n{code}\n```\n<contextual_information>\nWe have to export a \"main\" function like this: \"export async function main(...)\" and specify the parameter types but do not call it. You should generally return the result.\nYou can take as parameters resources which are dictionaries containing credentials or configuration information. Name the resource parameters like this: \"{resource_type}Resource\". \nThe following resource types are available:\n<resourceTypes>\n{resourceTypes}\n</resourceTypes>\nOnly define the type for resources that are actually needed to achieve the function purpose. The resource type name has to be exactly as specified. If the type name conflicts with the imported object, rename the imported object NOT THE TYPE.\nNaming conventions are guidelines, but follow the user's naming choices in the existing code.\n</contextual_information>\nI get the following error: {error}\nFix my code."
+        },
+        "bun": {
+            "prompt": "Here's my TypeScript code: \n```typescript\n{code}\n```\n<contextual_information>\nWe have to export a \"main\" function like this: \"export async function main(...)\" and specify the parameter types but do not call it. You should generally return the result.\nIf needed, the standard fetch method is available globally, do not import it.\nYou can take as parameters resources which are dictionaries containing credentials or configuration information. Name the resource parameters like this: \"{resource_type}Resource\".\nThe following resource types are available:\n<resourceTypes>\n{resourceTypes}\n</resourceTypes>\nOnly define the type for resources that are actually needed to achieve the function purpose. The resource type name has to be exactly as specified. If the type name conflicts with the imported object, rename the imported object NOT THE TYPE.\nNaming conventions are guidelines, but follow the user's naming choices in the existing code.\n</contextual_information>\nI get the following error: {error}\nFix my code."
+        },
+        "php": {
+            "prompt": "Here's my php code: \n```php\n{code}\n```\n<contextual_information>\nYou have to write a function in php called \"main\". Specify the parameter types. Do not call the main function. You should generally return the result. The script must start with `<?php`.\nYou can take as parameters resources which are classes containing credentials or configuration information. For Windmill to correctly detect the resources to be passed, the resource type name has to be exactly as specified in the following list:\n<resourceTypes>\n{resourceTypes}\n</resourceTypes>\nYou need to define the type of the resources that are needed before the main function, but only include them if they are actually needed to achieve the function purpose.\nBefore defining each type, check if the class already exists using class_exists.\nThe resource type name has to be exactly as specified.\nIf you need to import libraries, you need to specify them as comments in the following manner before the main function:\n```\n// require:\n// mylibrary/mylibrary\n// myotherlibrary/myotherlibrary@optionalversion\n```\nNo need to require autoload, it is already done.\n<contextual_information>\nI get the following error: {error}\nFix my code."
+        }
+    }
+};

package/package/components/copilot/prompts/gen.yaml

@@ -0,0 +1,191 @@
+system: |-
+  You are a helpful coding assistant for Windmill, a developer platform for running scripts. You write code as instructed by the user. Each user message includes some contextual information which should guide your answer.
+  Only output code. Wrap the code in a code block.
+  Put explanations directly in the code as comments.
+
+  Here's how interactions have to look like:
+  user: {sample_question}
+  assistant: ```language
+  {code}
+  ```
+prompts:
+  python3:
+    prompt: |-
+      <contextual_information>
+      You have to write a function in Python called "main". Specify the parameter types. Do not call the main function. You should generally return the result.
+      The "main" function cannot be async. If you need to use async code, you can use the asyncio library.
+      You can take as parameters resources which are dictionaries containing credentials or configuration information. For Windmill to correctly detect the resources to be passed, the resource type name has to be exactly as specified in the following list:
+      <resourceTypes>
+      {resourceTypes}
+      </resourceTypes>
+      You need to define the type of the resources that are needed before the main function, but only include them if they are actually needed to achieve the function purpose.
+      The resource type name has to be exactly as specified (has to be IN LOWERCASE). If the type name conflicts with any imported methods, you have to rename the imported method with the conflicting name.
+      <contextual_information>
+      My instructions: {description}
+  deno:
+    prompt: |-
+      <contextual_information>
+      You have to write TypeScript code and export a "main" function like this: "export async function main(...)" and specify the parameter types but do not call it. You should generally return the result.
+      You can import deno libraries or you can also import npm libraries like that: "import ... from "npm:{package}";". The fetch standard method is available globally.
+      You can take as parameters resources which are dictionaries containing credentials or configuration information. For Windmill to correctly detect the resources to be passed, the resource type name has to be exactly as specified in the following list:
+      <resourceTypes>
+      {resourceTypes}
+      </resourceTypes>
+      You need to define the type of the resources that are needed before the main function, but only include them if they are actually needed to achieve the function purpose.
+      The resource type name has to be exactly as specified (no resource suffix). If the type name conflicts with any imported methods, you have to rename the imported method with the conflicting name.
+      </contextual_information>
+      My instructions: {description}
+  rust:
+    prompt: |-
+      <contextual_information>
+      You have to write Rust code and define a `main` function like this (without calling it):
+      ```rust
+      pub fn main(...) -> Result<ReturnType, Box<dyn std::error::Error>>
+      ```
+      Favor idiomatic Rust patterns, ensuring safe ownership and borrowing, robust error handling with `Result`, and concurrency if needed (`async`/`tokio` or std threading).
+
+      Include only necessary imports and modules, and add comments explaining important operations. Provide at least one unit test using Rust's built-in test framework (`#[cfg(test)] mod tests { ... }`) to demonstrate correctness. Make the code well-formatted (similar to `cargo fmt` style). The generated code should be easily executable and testable in an integrated terminal.
+      </contextual_information>
+      My instructions: {description}
+  go:
+    prompt: |-
+      Here's my go code: 
+      ```go
+      {code}
+      ```
+      <contextual_information>
+      You have to write go code and export a "main" function. Import the packages you need. The return type of the function has to be ({return_type}, error). The file package has to be "inner"
+      </contextual_information>
+      My instructions: {description}
+  bash:
+    prompt: |-
+      <contextual_information>
+      You have to write bash code. Do not include "#!/bin/bash". Arguments are always string and can only be obtained with "var1="$1"", "var2="$2"", etc... You do not need to check if the arguments are present.
+      </contextual_information>
+      My instructions: {description}
+  postgresql:
+    prompt: |-
+      <contextual_information>
+      You have to write a statement for PostgreSQL. Arguments can be obtained directly in the statement with `$1::{type}`, `$2::{type}`, etc... Name the parameters (without specifying the type) by adding comments before the statement like that: `-- $1 name1` or `-- $2 name = default` (one per row)
+      </contextual_information>
+      My instructions: {description}
+  mysql:
+    prompt: |-
+      <contextual_information>
+      You have to write a statement for MySQL. Arguments can be obtained directly in the statement with ?. Name the parameters by adding comments before the statement like that: `-- ? name1 ({type})` or `-- ? name2 ({type}) = default` (one per row)
+      </contextual_information>
+      My instructions: {description}
+  bigquery:
+    prompt: |-
+      <contextual_information>
+      You have to write a statement for BigQuery. You can define arguments by adding comments before the statement like that: `-- @name1 ({type})` or `-- @name2 ({type}) = default` (one per row). They can then be obtained directly in the statement with `@name1`, `@name2`, etc....
+      </contextual_information>
+      My instructions: {description}
+  snowflake:
+    prompt: |-
+      <contextual_information>
+      You have to write a statement for Snowflake. Arguments can be obtained directly in the statement with ?. Name the parameters by adding comments before the statement like that: `-- ? name1 ({type})` or `-- ? name2 ({type}) = default` (one per row)
+      </contextual_information>
+      My instructions: {description}
+  mssql:
+    prompt: |-
+      <contextual_information>
+      You have to write a statement for Microsoft SQL Server. Arguments can be obtained directly in the statement with @P1, @P2, etc.. Name the parameters by adding comments before the statement like that: `-- @P1 name1 ({type})` or `-- @P2 name2 ({type}) = default` (one per row)
+      </contextual_information>
+      My instructions: {description}
+  graphql:
+    prompt: |-
+      <contextual_information>
+      You have to write a query for GraphQL. Add the needed arguments as query parameters.
+      </contextual_information>
+      My instructions: {description}
+  powershell:
+    prompt: |-
+      <contextual_information>
+      You have to write Powershell code. Arguments can be obtained by calling the param function on the first line like that: `param($ParamName1, $ParamName2 = "default value", [{type}]$ParamName3, ...)`
+      </contextual_information>
+      My instructions: {description}
+  nativets:
+    prompt: |-
+      <contextual_information>
+      You have to write TypeScript code and export a "main" function like this: "export async function main(...)" and specify the parameter types but do not call it. You should generally return the result.
+      You should use fetch and are not allowed to import any libraries. 
+      You can take as parameters resources which are dictionaries containing credentials or configuration information. For Windmill to correctly detect the resources to be passed, the resource type name has to be exactly as specified in the following list:
+      <resourceTypes>
+      {resourceTypes}
+      </resourceTypes>
+      You need to define the type of the resources that are needed before the main function, but only include them if they are actually needed to achieve the function purpose.
+      The resource type name has to be exactly as specified (no resource suffix).
+      </contextual_information>
+      My instructions: {description}
+  bun:
+    prompt: |-
+      <contextual_information>
+      You have to write TypeScript code and export a "main" function like this: "export async function main(...)" and specify the parameter types but do not call it. You should generally return the result.
+      The fetch standard method is available globally.
+      You can take as parameters resources which are dictionaries containing credentials or configuration information. For Windmill to correctly detect the resources to be passed, the resource type name has to be exactly as specified in the following list:
+      <resourceTypes>
+      {resourceTypes}
+      </resourceTypes>
+      You need to define the type of the resources that are needed before the main function, but only include them if they are actually needed to achieve the function purpose.
+      The resource type name has to be exactly as specified (no resource suffix). If the type name conflicts with any imported methods, you have to rename the imported method with the conflicting name.
+      </contextual_information>
+      My instructions: {description}
+  php:
+    prompt: |-
+      <contextual_information>
+      You have to write a function in php called "main". Specify the parameter types. Do not call the main function. You should generally return the result. The script must start with `<?php`.
+      You can take as parameters resources which are classes containing credentials or configuration information. For Windmill to correctly detect the resources to be passed, the resource type name has to be exactly as specified in the following list:
+      <resourceTypes>
+      {resourceTypes}
+      </resourceTypes>
+      You need to define the type of the resources that are needed before the main function, but only include them if they are actually needed to achieve the function purpose.
+      Before defining each type, check if the class already exists using class_exists.
+      The resource type name has to be exactly as specified.
+      If you need to import libraries, you need to specify them as comments in the following manner before the main function:
+      ```
+      // require:
+      // mylibrary/mylibrary
+      // myotherlibrary/myotherlibrary@optionalversion
+      ```
+      No need to require autoload, it is already done.
+      <contextual_information>
+      My instructions: {description}
+  frontend:
+    prompt: |-
+      Write client-side javascript code that should {description}. 
+
+      <contextual_information>
+      You can access the context object with the ctx global variable. 
+      The app state is a store that can be used to store data. You can access and update the state object with the state global variable like this: state.foo = 'bar'
+      You can use the goto function to navigate to a specific URL: goto(path: string, newTab?: boolean)
+      You can use the openModal and closeModal functions to open and close a modal: openModal(id: string), closeModal(id: string)
+      You can use the setTab function to manually set the tab of a Tab component: setTab(id: string, index: string)
+      You can use the recompute function to recompute a component: recompute(id: string)
+      You can use the getAgGrid function to get the ag-grid instance of a table: getAgGrid(id: string)
+      You can use the setSelectedIndex function to select a row in a table or an AG Grid table: setSelectedIndex(id: string, index: number)
+      The setValue function is meant to set or force the value of a component: setValue(id: string, value: any)
+      You can validate a specific field of a form: validate(id: string, key: string)
+      You can validate all fields of a form: validateAll(id: string, key: string)
+      You can invalidate a specific field of a form: invalidate(id: string, key: string, error: string)
+      </contextual_information>
+  transformer:
+    prompt: |-
+      Write client-side javascript code that should process the variable `result` according to the following instructions: {description}.
+      The variable `result` is available globally.
+      At the end of the code, the processed result has to be returned.
+
+      <contextual_information>
+      You can access the context object with the ctx global variable. 
+      The app state is a store that can be used to store data. You can access and update the state object with the state global variable like this: state.foo = 'bar'
+      You can use the goto function to navigate to a specific URL: goto(path: string, newTab?: boolean)
+      You can use the openModal and closeModal functions to open and close a modal: openModal(id: string), closeModal(id: string)
+      You can use the setTab function to manually set the tab of a Tab component: setTab(id: string, index: string)
+      You can use the recompute function to recompute a component: recompute(id: string)
+      You can use the getAgGrid function to get the ag-grid instance of a table: getAgGrid(id: string)
+      You can use the setSelectedIndex function to select a row in a table or an AG Grid table: setSelectedIndex(id: string, index: number)
+      The setValue function is meant to set or force the value of a component: setValue(id: string, value: any)
+      You can validate a specific field of a form: validate(id: string, key: string)
+      You can validate all fields of a form: validateAll(id: string, key: string)
+      You can invalidate a specific field of a form: invalidate(id: string, key: string, error: string)
+      </contextual_information>

package/package/components/copilot/prompts/genPrompt.d.ts

@@ -0,0 +1,56 @@
+export declare const GEN_PROMPT: {
+    system: string;
+    prompts: {
+        python3: {
+            prompt: string;
+        };
+        deno: {
+            prompt: string;
+        };
+        rust: {
+            prompt: string;
+        };
+        go: {
+            prompt: string;
+        };
+        bash: {
+            prompt: string;
+        };
+        postgresql: {
+            prompt: string;
+        };
+        mysql: {
+            prompt: string;
+        };
+        bigquery: {
+            prompt: string;
+        };
+        snowflake: {
+            prompt: string;
+        };
+        mssql: {
+            prompt: string;
+        };
+        graphql: {
+            prompt: string;
+        };
+        powershell: {
+            prompt: string;
+        };
+        nativets: {
+            prompt: string;
+        };
+        bun: {
+            prompt: string;
+        };
+        php: {
+            prompt: string;
+        };
+        frontend: {
+            prompt: string;
+        };
+        transformer: {
+            prompt: string;
+        };
+    };
+};

package/package/components/copilot/prompts/genPrompt.js

@@ -0,0 +1,56 @@
+export const GEN_PROMPT = {
+    "system": "You are a helpful coding assistant for Windmill, a developer platform for running scripts. You write code as instructed by the user. Each user message includes some contextual information which should guide your answer.\nOnly output code. Wrap the code in a code block.\nPut explanations directly in the code as comments.\n\nHere's how interactions have to look like:\nuser: {sample_question}\nassistant: ```language\n{code}\n```",
+    "prompts": {
+        "python3": {
+            "prompt": "<contextual_information>\nYou have to write a function in Python called \"main\". Specify the parameter types. Do not call the main function. You should generally return the result.\nThe \"main\" function cannot be async. If you need to use async code, you can use the asyncio library.\nYou can take as parameters resources which are dictionaries containing credentials or configuration information. For Windmill to correctly detect the resources to be passed, the resource type name has to be exactly as specified in the following list:\n<resourceTypes>\n{resourceTypes}\n</resourceTypes>\nYou need to define the type of the resources that are needed before the main function, but only include them if they are actually needed to achieve the function purpose.\nThe resource type name has to be exactly as specified (has to be IN LOWERCASE). If the type name conflicts with any imported methods, you have to rename the imported method with the conflicting name.\n<contextual_information>\nMy instructions: {description}"
+        },
+        "deno": {
+            "prompt": "<contextual_information>\nYou have to write TypeScript code and export a \"main\" function like this: \"export async function main(...)\" and specify the parameter types but do not call it. You should generally return the result.\nYou can import deno libraries or you can also import npm libraries like that: \"import ... from \"npm:{package}\";\". The fetch standard method is available globally.\nYou can take as parameters resources which are dictionaries containing credentials or configuration information. For Windmill to correctly detect the resources to be passed, the resource type name has to be exactly as specified in the following list:\n<resourceTypes>\n{resourceTypes}\n</resourceTypes>\nYou need to define the type of the resources that are needed before the main function, but only include them if they are actually needed to achieve the function purpose.\nThe resource type name has to be exactly as specified (no resource suffix). If the type name conflicts with any imported methods, you have to rename the imported method with the conflicting name.\n</contextual_information>\nMy instructions: {description}"
+        },
+        "rust": {
+            "prompt": "<contextual_information>\nYou have to write Rust code and define a `main` function like this (without calling it):\n```rust\npub fn main(...) -> Result<ReturnType, Box<dyn std::error::Error>>\n```\nFavor idiomatic Rust patterns, ensuring safe ownership and borrowing, robust error handling with `Result`, and concurrency if needed (`async`/`tokio` or std threading).\n\nInclude only necessary imports and modules, and add comments explaining important operations. Provide at least one unit test using Rust's built-in test framework (`#[cfg(test)] mod tests { ... }`) to demonstrate correctness. Make the code well-formatted (similar to `cargo fmt` style). The generated code should be easily executable and testable in an integrated terminal.\n</contextual_information>\nMy instructions: {description}"
+        },
+        "go": {
+            "prompt": "Here's my go code: \n```go\n{code}\n```\n<contextual_information>\nYou have to write go code and export a \"main\" function. Import the packages you need. The return type of the function has to be ({return_type}, error). The file package has to be \"inner\"\n</contextual_information>\nMy instructions: {description}"
+        },
+        "bash": {
+            "prompt": "<contextual_information>\nYou have to write bash code. Do not include \"#!/bin/bash\". Arguments are always string and can only be obtained with \"var1=\"$1\"\", \"var2=\"$2\"\", etc... You do not need to check if the arguments are present.\n</contextual_information>\nMy instructions: {description}"
+        },
+        "postgresql": {
+            "prompt": "<contextual_information>\nYou have to write a statement for PostgreSQL. Arguments can be obtained directly in the statement with `$1::{type}`, `$2::{type}`, etc... Name the parameters (without specifying the type) by adding comments before the statement like that: `-- $1 name1` or `-- $2 name = default` (one per row)\n</contextual_information>\nMy instructions: {description}"
+        },
+        "mysql": {
+            "prompt": "<contextual_information>\nYou have to write a statement for MySQL. Arguments can be obtained directly in the statement with ?. Name the parameters by adding comments before the statement like that: `-- ? name1 ({type})` or `-- ? name2 ({type}) = default` (one per row)\n</contextual_information>\nMy instructions: {description}"
+        },
+        "bigquery": {
+            "prompt": "<contextual_information>\nYou have to write a statement for BigQuery. You can define arguments by adding comments before the statement like that: `-- @name1 ({type})` or `-- @name2 ({type}) = default` (one per row). They can then be obtained directly in the statement with `@name1`, `@name2`, etc....\n</contextual_information>\nMy instructions: {description}"
+        },
+        "snowflake": {
+            "prompt": "<contextual_information>\nYou have to write a statement for Snowflake. Arguments can be obtained directly in the statement with ?. Name the parameters by adding comments before the statement like that: `-- ? name1 ({type})` or `-- ? name2 ({type}) = default` (one per row)\n</contextual_information>\nMy instructions: {description}"
+        },
+        "mssql": {
+            "prompt": "<contextual_information>\nYou have to write a statement for Microsoft SQL Server. Arguments can be obtained directly in the statement with @P1, @P2, etc.. Name the parameters by adding comments before the statement like that: `-- @P1 name1 ({type})` or `-- @P2 name2 ({type}) = default` (one per row)\n</contextual_information>\nMy instructions: {description}"
+        },
+        "graphql": {
+            "prompt": "<contextual_information>\nYou have to write a query for GraphQL. Add the needed arguments as query parameters.\n</contextual_information>\nMy instructions: {description}"
+        },
+        "powershell": {
+            "prompt": "<contextual_information>\nYou have to write Powershell code. Arguments can be obtained by calling the param function on the first line like that: `param($ParamName1, $ParamName2 = \"default value\", [{type}]$ParamName3, ...)`\n</contextual_information>\nMy instructions: {description}"
+        },
+        "nativets": {
+            "prompt": "<contextual_information>\nYou have to write TypeScript code and export a \"main\" function like this: \"export async function main(...)\" and specify the parameter types but do not call it. You should generally return the result.\nYou should use fetch and are not allowed to import any libraries. \nYou can take as parameters resources which are dictionaries containing credentials or configuration information. For Windmill to correctly detect the resources to be passed, the resource type name has to be exactly as specified in the following list:\n<resourceTypes>\n{resourceTypes}\n</resourceTypes>\nYou need to define the type of the resources that are needed before the main function, but only include them if they are actually needed to achieve the function purpose.\nThe resource type name has to be exactly as specified (no resource suffix).\n</contextual_information>\nMy instructions: {description}"
+        },
+        "bun": {
+            "prompt": "<contextual_information>\nYou have to write TypeScript code and export a \"main\" function like this: \"export async function main(...)\" and specify the parameter types but do not call it. You should generally return the result.\nThe fetch standard method is available globally.\nYou can take as parameters resources which are dictionaries containing credentials or configuration information. For Windmill to correctly detect the resources to be passed, the resource type name has to be exactly as specified in the following list:\n<resourceTypes>\n{resourceTypes}\n</resourceTypes>\nYou need to define the type of the resources that are needed before the main function, but only include them if they are actually needed to achieve the function purpose.\nThe resource type name has to be exactly as specified (no resource suffix). If the type name conflicts with any imported methods, you have to rename the imported method with the conflicting name.\n</contextual_information>\nMy instructions: {description}"
+        },
+        "php": {
+            "prompt": "<contextual_information>\nYou have to write a function in php called \"main\". Specify the parameter types. Do not call the main function. You should generally return the result. The script must start with `<?php`.\nYou can take as parameters resources which are classes containing credentials or configuration information. For Windmill to correctly detect the resources to be passed, the resource type name has to be exactly as specified in the following list:\n<resourceTypes>\n{resourceTypes}\n</resourceTypes>\nYou need to define the type of the resources that are needed before the main function, but only include them if they are actually needed to achieve the function purpose.\nBefore defining each type, check if the class already exists using class_exists.\nThe resource type name has to be exactly as specified.\nIf you need to import libraries, you need to specify them as comments in the following manner before the main function:\n```\n// require:\n// mylibrary/mylibrary\n// myotherlibrary/myotherlibrary@optionalversion\n```\nNo need to require autoload, it is already done.\n<contextual_information>\nMy instructions: {description}"
+        },
+        "frontend": {
+            "prompt": "Write client-side javascript code that should {description}. \n\n<contextual_information>\nYou can access the context object with the ctx global variable. \nThe app state is a store that can be used to store data. You can access and update the state object with the state global variable like this: state.foo = 'bar'\nYou can use the goto function to navigate to a specific URL: goto(path: string, newTab?: boolean)\nYou can use the openModal and closeModal functions to open and close a modal: openModal(id: string), closeModal(id: string)\nYou can use the setTab function to manually set the tab of a Tab component: setTab(id: string, index: string)\nYou can use the recompute function to recompute a component: recompute(id: string)\nYou can use the getAgGrid function to get the ag-grid instance of a table: getAgGrid(id: string)\nYou can use the setSelectedIndex function to select a row in a table or an AG Grid table: setSelectedIndex(id: string, index: number)\nThe setValue function is meant to set or force the value of a component: setValue(id: string, value: any)\nYou can validate a specific field of a form: validate(id: string, key: string)\nYou can validate all fields of a form: validateAll(id: string, key: string)\nYou can invalidate a specific field of a form: invalidate(id: string, key: string, error: string)\n</contextual_information>"
+        },
+        "transformer": {
+            "prompt": "Write client-side javascript code that should process the variable `result` according to the following instructions: {description}.\nThe variable `result` is available globally.\nAt the end of the code, the processed result has to be returned.\n\n<contextual_information>\nYou can access the context object with the ctx global variable. \nThe app state is a store that can be used to store data. You can access and update the state object with the state global variable like this: state.foo = 'bar'\nYou can use the goto function to navigate to a specific URL: goto(path: string, newTab?: boolean)\nYou can use the openModal and closeModal functions to open and close a modal: openModal(id: string), closeModal(id: string)\nYou can use the setTab function to manually set the tab of a Tab component: setTab(id: string, index: string)\nYou can use the recompute function to recompute a component: recompute(id: string)\nYou can use the getAgGrid function to get the ag-grid instance of a table: getAgGrid(id: string)\nYou can use the setSelectedIndex function to select a row in a table or an AG Grid table: setSelectedIndex(id: string, index: number)\nThe setValue function is meant to set or force the value of a component: setValue(id: string, value: any)\nYou can validate a specific field of a form: validate(id: string, key: string)\nYou can validate all fields of a form: validateAll(id: string, key: string)\nYou can invalidate a specific field of a form: invalidate(id: string, key: string, error: string)\n</contextual_information>"
+        }
+    }
+};

package/package/components/copilot/prompts/index.d.ts

@@ -0,0 +1,11 @@
+export interface PromptsConfig {
+    system: string;
+    prompts: {
+        [lang: string]: {
+            prompt: string;
+        };
+    };
+}
+export declare const EDIT_CONFIG: PromptsConfig;
+export declare const FIX_CONFIG: PromptsConfig;
+export declare const GEN_CONFIG: PromptsConfig;

package/package/components/copilot/prompts/index.js

@@ -0,0 +1,6 @@
+import { EDIT_PROMPT } from './editPrompt';
+import { FIX_PROMPT } from './fixPrompt';
+import { GEN_PROMPT } from './genPrompt';
+export const EDIT_CONFIG = EDIT_PROMPT;
+export const FIX_CONFIG = FIX_PROMPT;
+export const GEN_CONFIG = GEN_PROMPT;

package/package/components/copilot/prompts/yaml2json.py

@@ -0,0 +1,16 @@
+import yaml, json
+
+with open("gen.yaml", "r") as f:
+    promptConfig = json.dumps(yaml.load(f, Loader=yaml.CLoader), indent=2)
+    with open("genPrompt.ts", "w") as f2:
+        f2.write("export const GEN_PROMPT = " + promptConfig + ";")
+
+with open("edit.yaml", "r") as f:
+    promptConfig = json.dumps(yaml.load(f, Loader=yaml.CLoader), indent=2)
+    with open("editPrompt.ts", "w") as f2:
+        f2.write("export const EDIT_PROMPT = " + promptConfig + ";")
+
+with open("fix.yaml", "r") as f:
+    promptConfig = json.dumps(yaml.load(f, Loader=yaml.CLoader), indent=2)
+    with open("fixPrompt.ts", "w") as f2:
+        f2.write("export const FIX_PROMPT = " + promptConfig + ";")

package/package/components/copilot/utils.d.ts

@@ -0,0 +1,6 @@
+import type { Schema } from '../../common';
+import type { ResourceType } from '../../gen';
+export declare function pythonCompile(schema: Schema): string;
+export declare function phpCompile(schema: Schema): string;
+export declare function formatResourceTypes(resourceTypes: ResourceType[], lang: 'python3' | 'typescript' | 'php'): string;
+export declare function yamlStringifyExceptKeys(obj: any, keys: string[]): string;

package/package/components/copilot/utils.js

@@ -0,0 +1,130 @@
+import { capitalize, toCamel } from '../../utils';
+import YAML from 'yaml';
+function compile(schema) {
+    function rec(x, root = false) {
+        let res = '{\n';
+        const entries = Object.entries(x);
+        if (entries.length == 0) {
+            return 'any';
+        }
+        let i = 0;
+        for (let [name, prop] of entries) {
+            if (prop.type == 'object') {
+                res += `  ${name}: ${rec(prop.properties ?? {})}`;
+            }
+            else if (prop.type == 'array') {
+                res += `  ${name}: ${prop?.items?.type ?? 'any'}[]`;
+            }
+            else {
+                let typ = prop?.type ?? 'any';
+                if (typ == 'integer') {
+                    typ = 'number';
+                }
+                res += `  ${name}: ${typ}`;
+            }
+            i++;
+            if (i < entries.length) {
+                res += ',\n';
+            }
+        }
+        res += '\n}';
+        return res;
+    }
+    return rec(schema.properties, true);
+}
+export function pythonCompile(schema) {
+    let res = '';
+    const entries = Object.entries(schema.properties);
+    if (entries.length === 0) {
+        return 'dict';
+    }
+    let i = 0;
+    for (let [name, prop] of entries) {
+        let typ = 'dict';
+        if (prop.type === 'array') {
+            typ = 'list';
+        }
+        else if (prop.type === 'string') {
+            typ = 'str';
+        }
+        else if (prop.type === 'number') {
+            typ = 'float';
+        }
+        else if (prop.type === 'integer') {
+            typ = 'int';
+        }
+        else if (prop.type === 'boolean') {
+            typ = 'bool';
+        }
+        res += `    ${name}: ${typ}`;
+        i++;
+        if (i < entries.length) {
+            res += '\n';
+        }
+    }
+    return res;
+}
+export function phpCompile(schema) {
+    let res = '';
+    const entries = Object.entries(schema.properties);
+    if (entries.length === 0) {
+        return 'array';
+    }
+    let i = 0;
+    for (let [name, prop] of entries) {
+        let typ = 'array';
+        if (prop.type === 'array') {
+            typ = 'array';
+        }
+        else if (prop.type === 'string') {
+            typ = 'string';
+        }
+        else if (prop.type === 'number') {
+            typ = 'float';
+        }
+        else if (prop.type === 'integer') {
+            typ = 'int';
+        }
+        else if (prop.type === 'boolean') {
+            typ = 'bool';
+        }
+        res += `  public ${typ} $${name};`;
+        i++;
+        if (i < entries.length) {
+            res += '\n';
+        }
+    }
+    return res;
+}
+export function formatResourceTypes(resourceTypes, lang) {
+    if (lang === 'python3') {
+        const result = resourceTypes.map((resourceType) => {
+            return `class ${resourceType.name}(TypedDict):\n${pythonCompile(resourceType.schema)}`;
+        });
+        return '\n' + result.join('\n\n');
+    }
+    else if (lang === 'php') {
+        const result = resourceTypes.map((resourceType) => {
+            return `class ${toCamel(capitalize(resourceType.name))} {\n${phpCompile(resourceType.schema)}\n}`;
+        });
+        return '\n' + result.join('\n\n');
+    }
+    else {
+        const result = resourceTypes
+            .filter((resourceType) => Boolean(resourceType.schema) && typeof resourceType.schema === 'object')
+            .map((resourceType) => {
+            return `type ${toCamel(capitalize(resourceType.name))} = ${compile(resourceType.schema)}`;
+        });
+        return '\n' + result.join('\n\n');
+    }
+}
+export function yamlStringifyExceptKeys(obj, keys) {
+    return YAML.stringify(obj, (key, val) => {
+        if (keys.includes(key)) {
+            return undefined;
+        }
+        else {
+            return val;
+        }
+    });
+}