Initial import + refine generated PowerShell templates for HARD-001, …#3
Conversation
…HARD-010 and HARD-012
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 7e730f9c82
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| param( | ||
| [string]$SearchBase = "", | ||
| [string]$CsvPath = "" | ||
| ) |
There was a problem hiding this comment.
Move param block ahead of executable header statements
This new param(...) block is injected after SCRIPT_HEADER, which already emits executable statements (Set-StrictMode and $ErrorActionPreference) before template content, so generated scripts for HARD-001/HARD-010/HARD-012 place param too late in the file. In PowerShell, script-level param must appear before executable statements (aside from comments/#Requires), so these generated remediation scripts will fail to parse instead of running.
Useful? React with 👍 / 👎.
…HARD-010 and HARD-012
Summary
Describe the change clearly and factually.
Scope
Validation
List the commands, tests, or datasets used to validate the change.
Notes
State any limitation, compatibility concern, or follow-up work.