sf-cli-wrapper

Salesforce/sf-cli-wrapper

Fork 0

Commit Graph

Author	SHA1	Message	Date
Reynold Lariza	159ede3794	Standardize verbose parameter from -vb to -ve across all scripts - 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	2025-08-28 20:47:46 +08:00
reynold	f22a46d711	Complete two-character option consistency across remaining scripts 🎯 Final Consistency Implementation: ✅ Updated Scripts: - sf-org-info: -to, -vb, -ls, -hp (fixed array handling + options) - sf-check: -vb, -hp (environment verification) - sf-apex-run: -to, -fl, -cd, -hp (Apex execution) - sf-retrieve: -to, -tp, -nm, -mn, -pk, -dr, -hp (metadata retrieval) - sf-test-run: -to, -cn, -sn, -al, -lv, -cv, -wt, -hp (test execution) 🔧 Key Changes: - Replaced ALL single-character options with two-character equivalents - Updated argument parsing from getopts to manual parsing - Fixed help text and error messages to use new options - Updated example commands and references 📊 Consistency Status: - 12/12 scripts now use uniform two-character options - 0/12 scripts have conflicting option styles - 100% consistency achieved across entire toolkit 🚀 Benefits Delivered: - No more confusion between scripts - Predictable and self-documenting options - Professional user experience - Ready for production deployment	2025-08-28 19:04:07 +08:00
reynold	a385484a69	updated scripts	2025-08-28 15:51:17 +08:00

Author

SHA1

Message

Date

Reynold Lariza

159ede3794

Standardize verbose parameter from -vb to -ve across all scripts

- 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

2025-08-28 20:47:46 +08:00

reynold

f22a46d711

Complete two-character option consistency across remaining scripts

🎯 Final Consistency Implementation:

✅ Updated Scripts:
  - sf-org-info: -to, -vb, -ls, -hp (fixed array handling + options)
  - sf-check: -vb, -hp (environment verification)
  - sf-apex-run: -to, -fl, -cd, -hp (Apex execution)
  - sf-retrieve: -to, -tp, -nm, -mn, -pk, -dr, -hp (metadata retrieval)
  - sf-test-run: -to, -cn, -sn, -al, -lv, -cv, -wt, -hp (test execution)

🔧 Key Changes:
  - Replaced ALL single-character options with two-character equivalents
  - Updated argument parsing from getopts to manual parsing
  - Fixed help text and error messages to use new options
  - Updated example commands and references

📊 Consistency Status:
  - 12/12 scripts now use uniform two-character options
  - 0/12 scripts have conflicting option styles
  - 100% consistency achieved across entire toolkit

🚀 Benefits Delivered:
  - No more confusion between scripts
  - Predictable and self-documenting options
  - Professional user experience
  - Ready for production deployment

2025-08-28 19:04:07 +08:00

reynold

a385484a69

updated scripts

2025-08-28 15:51:17 +08:00

3 Commits