Migrate `spo sitedesign` commands to Zod
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- TypeScript
- Stars
- 1.5k
- Forks
- 413
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 21
Description
Part of #6807
Commands to migrate:
-
spo sitedesign add -
spo sitedesign apply -
spo sitedesign get -
spo sitedesign list -
spo sitedesign remove -
spo sitedesign rights grant -
spo sitedesign rights list -
spo sitedesign rights revoke -
spo sitedesign run list -
spo sitedesign run status get -
spo sitedesign set -
spo sitedesign task get -
spo sitedesign task list -
spo sitedesign task remove
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the migration guidance in #6807 and the existing implementations of the listed spo sitedesign command entry points. Work through the checklist, covering all 14 commands and their nested rights, run, and task subcommands. Done means each listed command has migrated to Zod without changing its existing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100