Replace UniqueId with "unique ID" in command docs
Maintainers usually reply within 2 days
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 75/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- cli, documentation
Research direction
Search the command documentation for UniqueId across the commands listed in the issue and review their option descriptions and examples. Replace each instance with “unique ID,” then check those command docs to confirm the wording is consistent and no listed command was missed.
Written by the indexing model from the issue text.
Description
Several command docs use UniqueId in option descriptions and examples, like The UniqueId (GUID) of the file.... UniqueId is not really a word, so we should use "unique ID" instead.
This was raised in a review of the archive/unarchive commands and fixed there. The same wording is still used in several other commands.
This issue is to fix the following commands:
- spo file checkin
- spo file checkout
- spo file checkout undo
- spo file copy
- spo file get
- spo file retentionlabel ensure
- spo file retentionlabel remove
- spo file roleassignment add
- spo file roleassignment remove
- spo file roleinheritance break
- spo file roleinheritance reset
- spo file sharinginfo get
- spo file sharinglink add
- spo file sharinglink clear
- spo file sharinglink get
- spo file sharinglink list
- spo file sharinglink remove
- spo file sharinglink set
- spo file version clear
- spo file version get
- spo file version keep
- spo file version list
- spo file version remove
- spo file version restore
- spo folder copy
- spo folder get
- spo folder retentionlabel ensure
- spo folder retentionlabel remove
- spo folder sharinglink add
- spo folder sharinglink list
- spo folder sharinglink remove
- spp model get
- spp model remove
- Dominant language
- TypeScript
- Stars
- 1.5k
- Forks
- 414
- Avg merge
- 5d 12h
- Merged PRs (30d)
- 14
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from pnp/cli-microsoft365
-
Bug report: app-only certificate login crashes with internal assertion when the token has no `oid` claim (service principal missing)Possibly taken @kkaminsk claimed this 23 days ago. Openbug needs peer review
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
pnp/cli-microsoft365#7589 ·
Maintainers usually reply within 2 days
-
Minimal permissions for 'viva engage message' commandsPossibly taken @Sarthak-Shreshtha01 claimed this 18 days ago. Opendocs work in progress
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
pnp/cli-microsoft365#7537 · 1 comment · 1 assignee ·
Maintainers usually reply within 2 days
-
docs help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
pnp/cli-microsoft365#7535 ·
Maintainers usually reply within 2 days
-
Minimal permissions for 'teams user app' commandsPossibly taken @SmitaNachan claimed this 6 days ago. Opendocs work in progress
Difficulty 2/5 1-2 days Newbie friendliness 78/100
pnp/cli-microsoft365#7529 · 1 comment · 1 assignee ·
Maintainers usually reply within 2 days
-
docs help wanted
Difficulty 2/5 1-2 days Newbie friendliness 78/100
pnp/cli-microsoft365#7507 ·
Maintainers usually reply within 2 days
All issues in pnp/cli-microsoft365
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
vercel/streamdown#673 · 1 reaction ·
Maintainers usually reply within 1 day
-
docs(stream-protocol): document messageMetatadata on start/finish and the message-metadata chunkOpenfactory-active task-identify-harness-labels-done task-identify-issue-type-done
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
agilepathway/label-checker#721 ·
Maintainers usually reply within 1 day
-
CLI Empathy needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
chromaui/chromatic-cli#1524 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day