wasp/waspc/data/Lsp/templates/ts/action.fn.ts

import { {{upperDeclName}} } from 'wasp/server/actions/types'

type {{upperDeclName}}Input = void
type {{upperDeclName}}Output = void

{{#named?}}export {{/named?}}const {{name}}: {{upperDeclName}}<{{upperDeclName}}Input, {{upperDeclName}}Output> = async (args, context) => {
  // Implementation goes here
}

{{#default?}}
export default {{name}}
{{/default?}}
Update LSP to work with restructuring (#1650) 2024-01-29 18:05:56 +03:00			`import { {{upperDeclName}} } from 'wasp/server/actions/types'`
[waspls] Add code actions for scaffolding external code (#1316) When an external import tries to import a symbol from a TypeScript/JavaScript file, waspls now offers quickfix code actions to scaffold a function in that file. It uses the surrounding context of the external import to determine what code to write for the code action. See [`ScaffoldTsSymbol.hs`](https://github.com/wasp-lang/wasp/blob/457911d5e99a98dd123940e6b0730b147636f411/waspc/waspls/src/Wasp/LSP/Commands/ScaffoldTsSymbol.hs) for a detailed description of how it works. At a high level, there is a `templateForFile` function in `Wasp.LSP.Commands.ScaffoldTsSymbol` that selects the correct template from `data/lsp/templates/ts`. For example, `action.fn.ts` contains a template for scaffolding an `action` function in a TypeScript file and would be used when a code action is requested with the cursor at the location marked by `\|`: ```wasp action createTask { fn: import { createTask } from "@server/actions.js"\| } ``` The scaffold action runs as a [LSP command](https://microsoft.github.io/language-server-protocol/specifications/specification-3-16/#workspace_executeCommand). To prepare for wanting to define more commands in waspls in the future, this PR also introduces the concept of `Commands` (`Wasp.LSP.Commands.Command`) that define some properties about each command waspls wants to handle. 2023-07-26 15:00:16 +03:00
[waspls] improves LSP scaffolding (#1381) * create directories when scaffolding, if needed * refresh export cache after scaffolding * better process for ensuring a blank line between old code and new scaffolded code 2023-08-10 17:01:20 +03:00			`type {{upperDeclName}}Input = void`
			`type {{upperDeclName}}Output = void`

			`{{#named?}}export {{/named?}}const {{name}}: {{upperDeclName}}<{{upperDeclName}}Input, {{upperDeclName}}Output> = async (args, context) => {`
[waspls] Add code actions for scaffolding external code (#1316) When an external import tries to import a symbol from a TypeScript/JavaScript file, waspls now offers quickfix code actions to scaffold a function in that file. It uses the surrounding context of the external import to determine what code to write for the code action. See [`ScaffoldTsSymbol.hs`](https://github.com/wasp-lang/wasp/blob/457911d5e99a98dd123940e6b0730b147636f411/waspc/waspls/src/Wasp/LSP/Commands/ScaffoldTsSymbol.hs) for a detailed description of how it works. At a high level, there is a `templateForFile` function in `Wasp.LSP.Commands.ScaffoldTsSymbol` that selects the correct template from `data/lsp/templates/ts`. For example, `action.fn.ts` contains a template for scaffolding an `action` function in a TypeScript file and would be used when a code action is requested with the cursor at the location marked by `\|`: ```wasp action createTask { fn: import { createTask } from "@server/actions.js"\| } ``` The scaffold action runs as a [LSP command](https://microsoft.github.io/language-server-protocol/specifications/specification-3-16/#workspace_executeCommand). To prepare for wanting to define more commands in waspls in the future, this PR also introduces the concept of `Commands` (`Wasp.LSP.Commands.Command`) that define some properties about each command waspls wants to handle. 2023-07-26 15:00:16 +03:00			`// Implementation goes here`
			`}`

			`{{#default?}}`
			`export default {{name}}`
			`{{/default?}}`