Pool Command

Post-Scaffold Checklist

After scaffolding, update the generated files:

• Command file: Add pool-specific flags (e.g. target-dev-hub, pool-name), typed result, business logic
• Message file: Replace placeholder strings with real summaries, descriptions, and examples
• Test file: Add sandbox stubs (TestContext, stubSfCommandUx) and meaningful assertions
• Use kebab-case for flag names, camelCase in code
• Use SfError from @salesforce/core for error handling
• Add logging at key lifecycle points (this.log() / this.debug())

Shared Logic (src/lib/)

If the command requires non-trivial business logic (org creation, pool state queries, config validation), extract it to src/lib/:

• Keep the command file thin: parse flags → call lib → format output
• Library code uses @salesforce/core/Logger, not this.log()
• Accept dependencies as parameters for testability
• See .github/instructions/lib.instructions.md for full conventions

Test Fixtures

Use config/pool-example.json as a reference pool configuration for tests and validation.

Acceptance Criteria

• Command extends SfCommand
• Errors use SfError from @salesforce/core
• All user-facing strings are in the message file
• --json output returns the typed result object
• Flags use kebab-case
• Key lifecycle points have logging (this.log() / this.debug())
• Non-trivial logic extracted to src/lib/