Skip to content

Commit

Permalink
prompt fixes /changes
Browse files Browse the repository at this point in the history
  • Loading branch information
potatoqualitee committed Oct 18, 2024
1 parent ce83dc5 commit 29e6002
Show file tree
Hide file tree
Showing 2 changed files with 11 additions and 1 deletion.
10 changes: 10 additions & 0 deletions .aider/prompts/fix-parms.ps1
Original file line number Diff line number Diff line change
@@ -0,0 +1,10 @@
# loop through all files in the tests directory that matches HaveParameter
$tests = Get-ChildItem -Path /workspace/tests -Filter *.Tests.ps1

$prompt = "When testing HaveParameter, we should have used type full names and we used type short names.Consult types.md and apply the appropriate replacements. Do not remove any arrays ([]), just replace the type names."


foreach ($test in $tests) {
Write-Host "Processing $test"
aider --message "$prompt" --file $test.FullName --model azure/gpt-4o-mini --no-stream --cache-prompts --read /workspace/.aider/prompts/types.md
}
2 changes: 1 addition & 1 deletion .aider/prompts/fix-template.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
Analyze and update the Pester test file for the dbatools PowerShell module at /workspace/tests/--CMDNAME--.Tests.ps1. Focus on the following:

1. Review the provided errors and their line numbers.
2. ONLY FOR SCOPING ERRORS: We should have used type full names and we used type short names. For any type errors, consult types.md and apply the appropriate replacements. Do not remove any arrays ([]), just replace the type names. Do not replace type names not causing errors.
2. ONLY FOR TYPE ERRORS: We should have used type full names and we used type short names. For any type errors, consult types.md and apply the appropriate replacements. Do not remove any arrays ([]), just replace the type names. Do not replace type names not causing errors.
3. Remember these are primarily INTEGRATION tests. Only mock when absolutely necessary.
4. Make minimal changes required to make the tests pass. Avoid over-engineering.
5. For SQL Server-specific testing scenarios, implement necessary adjustments while preserving test integrity.
Expand Down

0 comments on commit 29e6002

Please sign in to comment.