- Update all Bash scripts (sf-check, sf-org-info, sf-data-export, sf-data-import, sf-logs-tail) to use -ve instead of -vb
- Update all PowerShell scripts (sf-org-info.ps1, sf-apex-run.ps1, sf-check.ps1, sf-data-export.ps1, sf-data-import.ps1) to use -ve instead of -vb
- Fix PowerShell parameter conflicts with built-in -Verbose parameter
- Update README.md, TESTING.md, and OPTION_CONSISTENCY.md documentation to reflect -ve parameter
- Update test scripts (test-wrapper-suite.sh, test-wrapper-suite.ps1, test-all-wrappers.sh) to use -ve
- Maintain cross-platform consistency with two-character option scheme
- Fix Unicode display issues in PowerShell output with UTF-8 encoding
🔄 PowerShell Option Consistency - Phase 1 Complete:
✅ Updated Scripts:
- sf-deploy.ps1: -to, -sr, -dr, -ts, -hp (matches Bash)
- sf-dry-run.ps1: -to, -sr, -dr, -ts, -hp (matches Bash)
- sf-web-open.ps1: -to, -pt, -ur, -hp (matches Bash)
- sf-check.ps1: -vb, -hp (matches Bash)
- sf-org-create.ps1: -al, -dd, -df, -st, -tp, -hp (matches Bash)
🎯 Consistency Achieved:
- All parameter names now match their Bash counterparts exactly
- Help text updated with descriptive option names
- Examples updated to show new two-character options
- All validation logic updated to use new parameter names
🚀 Cross-Platform Alignment:
- PowerShell and Bash scripts now have identical option schemes
- Users get consistent experience across platforms
- No more confusion between single-char and two-char options
Remaining: 7 more PowerShell scripts to update for full consistency.
