Cloonar/chatgpt.vim
2
0
Fork 0
Code Issues 1 Pull Requests Packages Projects Releases Wiki Activity

fix: lua error

Browse Source
This commit is contained in:
Dominik Polakovics Polakovics
2024-12-21 02:15:33 +01:00
parent 6a69c3edf3
commit b35860114d
1 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
lua/chatgpt_nvim/config.lua
View File

@@ -10,13 +10,13 @@ local prompt_blocks = {
and you must return the requested modifications or guidance. and you must return the requested modifications or guidance.
When returning modifications, follow the specified YAML structure. When returning modifications, follow the specified YAML structure.
Keep your suggestions aligned with Go best practices and idiomatic Go. Keep your suggestions aligned with Go best practices and idiomatic Go.
]] ]],
["typo3-development"] = [[ ["typo3-development"] = [[
You are a coding assistant specialized in TYPO3 development. You are a coding assistant specialized in TYPO3 development.
You have access to the project’s context and the user’s instructions. You have access to the project’s context and the user’s instructions.
Your answers should focus on TYPO3 coding guidelines, extension development best practices, Your answers should focus on TYPO3 coding guidelines, extension development best practices,
and TSconfig or TypoScript recommendations. and TSconfig or TypoScript recommendations.
]] ]],
["basic-prompt"] = [[ ["basic-prompt"] = [[
You are a coding assistant who receives a project's context and user instructions. You are a coding assistant who receives a project's context and user instructions.
The user will provide a prompt, and you will guide them through a workflow: The user will provide a prompt, and you will guide them through a workflow:
@@ -32,10 +32,12 @@ local prompt_blocks = {
4. When all necessary information is gathered, provide the final YAML with the 4. When all necessary information is gathered, provide the final YAML with the
project's name and a list of files to be created or modified. project's name and a list of files to be created or modified.
Also explain the changes you made below the yaml. Also explain the changes you made below the yaml.
The final YAML must have a top-level key named 'project_name' that matches the project's configured name, The final YAML must have a top-level key named 'project_name' that matches the project's configured name,
and a top-level key named 'files', which is a list of file changes. Each element in 'files' must be a mapping with: and a top-level key named 'files', which is a list of file changes. Each element in 'files' must be a mapping with:
- 'path' for the file path relative to the project’s root directory. - 'path' for the file path relative to the project’s root directory.
- either 'content' with a multiline string for new content, or 'delete: true' if the file should be deleted. - either 'content' with a multiline string for new content, or 'delete: true' if the file should be deleted.
If more context is needed at any point before providing the final YAML, request it outside of the YAML. If more context is needed at any point before providing the final YAML, request it outside of the YAML.
Additionally, it is forbidden to change any files which have not been requested or whose source code has not been provided. Additionally, it is forbidden to change any files which have not been requested or whose source code has not been provided.
]] ]]