starred/windmill
1
0
Fork 0
mirror of https://github.com/windmill-labs/windmill.git synced 2026-08-18 16:02:10 +00:00
Code Issues Packages Projects Releases Wiki Activity

Grammar fixes (#2001)

Browse Source 
* Fix typos

* Fix TypeScript capitalization

* Fix log in verb

* Fix log out verb

---------

Co-authored-by: Faton Ramadani <faton.ramadani14@gmail.com>
This commit is contained in:
Dave Nicolson
2023-08-08 12:02:51 +02:00
committed by GitHub
parent 307c3bb9a6
commit b65fdb8b67
13 changed files with 27 additions and 27 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+2 -2
View File
@@ -8,7 +8,7 @@
Open-source developer infrastructure for internal tools. Self-hostable alternative to Airplane, Pipedream, Superblocks and a simplified Temporal with autogenerated UIsm and custom UIs to trigger workflows and scripts as internal apps.
<p align=center>
Scripts are turned into UIs and no-code modules, no-code modules can be composed into very rich flows, and script and flows can be triggered from internal UIs made with a low-code builder. The script languages supported are: Python, Typescript, Go, Bash, SQL. Scripts can be generated by an AI assistant powered by OpenAI.
Scripts are turned into UIs and no-code modules, no-code modules can be composed into very rich flows, and script and flows can be triggered from internal UIs made with a low-code builder. The script languages supported are: Python, TypeScript, Go, Bash, SQL. Scripts can be generated by an AI assistant powered by OpenAI.
</p>
<p align="center">
@@ -73,7 +73,7 @@ https://github.com/windmill-labs/windmill/assets/122811744/0b132cd1-ee67-4505-82
## Main Concepts
1. Define a minimal and generic script in Python, Typescript, Go or Bash that
1. Define a minimal and generic script in Python, TypeScript, Go or Bash that
solves a specific task. Here sending a POST request. The code can be defined
in the provided Web IDE or synchronized with your own github repo:
![Step 1](./imgs/windmill-editor.png)
backend/parsers/windmill-parser-ts/src/lib.rs
+1 -1
View File
@@ -44,7 +44,7 @@ pub fn parse_deno_signature(code: &str, skip_dflt: bool) -> anyhow::Result<MainA
let ast = parser
.parse_module()
.map_err(|_| anyhow::anyhow!("Error while parsing code, it is invalid typescript"))?
.map_err(|_| anyhow::anyhow!("Error while parsing code, it is invalid TypeScript"))?
.body;
let params = ast.into_iter().find_map(|x| match x {
frontend/src/lib/common.ts
+1 -1
View File
@@ -78,7 +78,7 @@ export function pathToMeta(path: string): Meta {
export function prettyLanguage(lang: string) {
switch (lang) {
case 'nativets':
return 'Native Typescript'
return 'Native TypeScript'
default:
return lang.charAt(0).toUpperCase() + lang.slice(1)
}
frontend/src/lib/components/ScriptBuilder.svelte
+2 -2
View File
@@ -61,7 +61,7 @@
}
const langs: [string, SupportedLanguage][] = [
['Typescript (Deno)', Script.language.DENO],
['TypeScript (Deno)', Script.language.DENO],
['Python', Script.language.PYTHON3]
]
if (SCRIPT_SHOW_BASH) {
@@ -393,7 +393,7 @@
}}
>
<LanguageIcon lang={Script.language.BUN} /><span class="ml-2 py-2 truncate">
Typescript (Bun, experimental)
TypeScript (Bun, experimental)
</span>
</Button>
frontend/src/lib/components/codeGen/prompts/edit.yaml
+3 -3
View File
@@ -17,7 +17,7 @@ prompts:
My instructions: {description}
deno:
prompt: |-
Here's my typescript code in a deno running environement:
Here's my TypeScript code in a deno running environment:
```typescript
{code}
```
@@ -59,7 +59,7 @@ prompts:
My instructions: {description}
nativets:
prompt: |-
Here's my typescript code:
Here's my TypeScript code:
```typescript
{code}
```
@@ -70,7 +70,7 @@ prompts:
My instructions: {description}
bun:
prompt: |-
Here's my typescript code in a node.js running environment:
Here's my TypeScript code in a node.js running environment:
```typescript
{code}
```
frontend/src/lib/components/codeGen/prompts/fix.yaml
+4 -4
View File
@@ -7,7 +7,7 @@ system: |-
explanation: "Here's the explanation"
Also put the explanations in the code as comments.
prompt: |-
Here's my environement: {environment}
Here's my environment: {environment}
Here's my code:
```{lang}
{code}
@@ -28,7 +28,7 @@ prompts:
Fix my code.
deno:
prompt: |-
Here's my typescript code in a deno running environement:
Here's my TypeScript code in a deno running environment:
```typescript
{code}
```
@@ -75,7 +75,7 @@ prompts:
Fix my code.
nativets:
prompt: |-
Here's my typescript code:
Here's my TypeScript code:
```typescript
{code}
```
@@ -87,7 +87,7 @@ prompts:
Fix my code.
bun:
prompt: |-
Here's my typescript code in a node.js running environment:
Here's my TypeScript code in a node.js running environment:
```typescript
{code}
```
frontend/src/lib/components/codeGen/prompts/gen.yaml
+3 -3
View File
@@ -12,7 +12,7 @@ prompts:
Only use the ones you need. If the TypedDict name conflicts with the imported object, rename the imported object NOT THE TYPE.
deno:
prompt: |-
Write a function in typescript called "main". The function should {description}. Specify the parameter types. You are in a Deno environment. You can import deno libraries or you can also import npm libraries like that: "import ... from "npm:{package}";". Export the "main" function like this: "export async function main(...)". Do not call the main function.
Write a function in TypeScript called "main". The function should {description}. Specify the parameter types. You are in a Deno environment. You can import deno libraries or you can also import npm libraries like that: "import ... from "npm:{package}";". Export the "main" function like this: "export async function main(...)". Do not call the main function.
You have access to the following resource types, if you need them, you have to define the type exactly as specified and add them as parameters: {resourceTypes}
Only use the ones you need. If the type name conflicts with the imported object, rename the imported object NOT THE TYPE.
go:
@@ -29,12 +29,12 @@ prompts:
Write SQL code for MySQL that should {description}. Arguments can be obtained directly in the statement with ?. Name the parameters by adding comments before the command like that: -- ? name1 ({type}) (one per row)
nativets:
prompt: |-
Write a function in typescript called "main". The function should {description}. Specify the parameter types. You should use fetch and are not allowed to import any libraries. Export the "main" function like this: "export async function main(...)". Do not call the main function.
Write a function in TypeScript called "main". The function should {description}. Specify the parameter types. You should use fetch and are not allowed to import any libraries. Export the "main" function like this: "export async function main(...)". Do not call the main function.
You have access to the following resource types, if you need them, you have to define the type exactly as specified and add them as parameters: {resourceTypes}
Only use the ones you need. If the type name conflicts with the imported object, rename the imported object NOT THE TYPE.
bun:
prompt: |-
Write a function in typescript called "main". The function should {description}. Specify the parameter types. You are in a Node.js environment. You can import npm libraries. Export the "main" function like this: "export async function main(...)". Do not call the main function.
Write a function in TypeScript called "main". The function should {description}. Specify the parameter types. You are in a Node.js environment. You can import npm libraries. Export the "main" function like this: "export async function main(...)". Do not call the main function.
You have access to the following resource types, if you need them, you have to define the type exactly as specified and add them as parameters: {resourceTypes}
Only use the ones you need. If the type name conflicts with the imported object, rename the imported object NOT THE TYPE.
frontend:
frontend/src/routes/(root)/(logged)/user/(user)/login/+page.js
+1 -1
View File
@@ -1,5 +1,5 @@
export function load() {
return {
stuff: { title: 'Login' }
stuff: { title: 'Log in' }
}
}
frontend/src/routes/(root)/(logged)/user/(user)/login/+page.svelte
+3 -3
View File
@@ -167,10 +167,10 @@
<WindmillIcon height="80px" width="80px" spin="slow" />
</div>
<h2 class="mt-6 text-center text-3xl font-bold tracking-tight text-primary">
Login or sign up
Log in or sign up
</h2>
<p class="mt-2 text-center text-sm text-secondary">
Login or sign up with any of the methods below
Log in or sign up with any of the methods below
</p>
</div>
@@ -233,7 +233,7 @@
showPassword = !showPassword
}}
>
Login without third-party
Log in without third-party
</Button>
</div>
{/if}
frontend/src/routes/(root)/(logged)/user/(user)/logout/+page.js
+1 -1
View File
@@ -1,5 +1,5 @@
export function load() {
return {
stuff: { title: 'Logout' }
stuff: { title: 'Log out' }
}
}
frontend/src/routes/(root)/(logged)/user/(user)/workspaces/+page.svelte
+1 -1
View File
@@ -232,7 +232,7 @@
logout()
}}
>
Logout
Log out
</Button>
</div>
</CenteredModal>
frontend/tests/global-setup.ts
+1 -1
View File
@@ -8,7 +8,7 @@ async function globalSetup() {
if (await page.locator('#email').isHidden()) {
await page.locator('button', {
hasText: 'Login without third-party'
hasText: 'Log in without third-party'
}).click()
}
llm/sample_answers.yaml
+4 -4
View File
@@ -171,7 +171,7 @@
description: Convert a number to a word
lang: deno
template_prompt: |-
Write a function in typescript called "main". The function should {description}. Specify the parameter types. You are in a Deno environment. You can import deno libraries or you can also import npm libraries like that: "import ... from "npm:{package}";". Export the "main" function like this: "export async function main(...)". Do not call the main function.
Write a function in TypeScript called "main". The function should {description}. Specify the parameter types. You are in a Deno environment. You can import deno libraries or you can also import npm libraries like that: "import ... from "npm:{package}";". Export the "main" function like this: "export async function main(...)". Do not call the main function.
You have access to the following resource types, if you need them, you have to define the type exactly as specified and add them as parameters: {resourceTypes}
Only use the ones you need. If the type name conflicts with the imported object, rename the imported object NOT THE TYPE.
template_system: |-
@@ -227,7 +227,7 @@
description: Connect to postgres and list the rows in the orders table
lang: deno
template_prompt: |-
Write a function in typescript called "main". The function should {description}. Specify the parameter types. You are in a Deno environment. You can import deno libraries or you can also import npm libraries like that: "import ... from "npm:{package}";". Export the "main" function like this: "export async function main(...)". Do not call the main function.
Write a function in TypeScript called "main". The function should {description}. Specify the parameter types. You are in a Deno environment. You can import deno libraries or you can also import npm libraries like that: "import ... from "npm:{package}";". Export the "main" function like this: "export async function main(...)". Do not call the main function.
You have access to the following resource types, if you need them, you have to define the type exactly as specified and add them as parameters: {resourceTypes}
Only use the ones you need. If the type name conflicts with the imported object, rename the imported object NOT THE TYPE.
template_system: |-
@@ -257,7 +257,7 @@
description: Convert a number to a word
lang: bun
template_prompt: |-
Write a function in typescript called "main". The function should {description}. Specify the parameter types. You are in a Node.js environment. You can import npm libraries. Export the "main" function like this: "export async function main(...)". Do not call the main function.
Write a function in TypeScript called "main". The function should {description}. Specify the parameter types. You are in a Node.js environment. You can import npm libraries. Export the "main" function like this: "export async function main(...)". Do not call the main function.
You have access to the following resource types, if you need them, you have to define the type exactly as specified and add them as parameters: {resourceTypes}
Only use the ones you need. If the type name conflicts with the imported object, rename the imported object NOT THE TYPE.
template_system: |-
@@ -411,7 +411,7 @@
description: Query the github api and return the number of stars of a repo
lang: nativets
template_prompt: |-
Write a function in typescript called "main". The function should {description}. Specify the parameter types. You should use fetch and are not allowed to import any libraries. Export the "main" function like this: "export async function main(...)". Do not call the main function.
Write a function in TypeScript called "main". The function should {description}. Specify the parameter types. You should use fetch and are not allowed to import any libraries. Export the "main" function like this: "export async function main(...)". Do not call the main function.
You have access to the following resource types, if you need them, you have to define the type exactly as specified and add them as parameters: {resourceTypes}
Only use the ones you need. If the type name conflicts with the imported object, rename the imported object NOT THE TYPE.
template_system: |-