Migrate `viva` 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:
-
viva connections app create -
viva engage community add -
viva engage community get -
viva engage community list -
viva engage community remove -
viva engage community set -
viva engage message add -
viva engage message get -
viva engage message like set -
viva engage message list -
viva engage message remove -
viva engage network list -
viva engage report activitycounts -
viva engage report activityusercounts -
viva engage report activityuserdetail -
viva engage report deviceusagedistributionusercounts -
viva engage report deviceusageusercounts -
viva engage report deviceusageuserdetail -
viva engage report groupsactivitycounts -
viva engage report groupsactivitydetail -
viva engage report groupsactivitygroupcounts -
viva engage role list -
viva engage search -
viva engage user get -
viva engage user list
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 locating the implementations and validation patterns for the listed viva commands, then compare them with existing Zod migrations in the project. The work is complete when every checked command in the list has been migrated to Zod and the command behavior remains covered by the project's relevant checks.
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
- 45/100