Skip to content

Include response output of a command in docs #3754

@Adam-it

Description

@Adam-it

💡Idea

The basic idea is to include command output in the command's doc.

🤔 Things to consider

General pointers

  • We display every output format (JSON, Text, CSV)
  • We normalize the data. For example, URLs are converted to 'contoso' as the tenant name
  • We change any personal information included in the output
  • If an option A returns a different output as option B, then we include both results
  • If the command doesn't return an ouput. We write The command won't return a response on success.
  • We added the Response header below the Examples header
  • We make sure the *.md file always ends on a new line
  • We don't shorten the ouput for readability
  • Every list command will contain [ ] and a single reponse within the JSON output.

Examples

We can go on and on about the pointers but an example explains it much beter than written text. Below you'll find different examples for different scenarios. If you're missing a scenario, don't be afraid to ask us 😉

  • A single object response (planner plan get)

The docs article
The MarkDown file location

  • An object list response (planner plan list)

The docs article
The MarkDown file location

Note: Make sure the Text output is also in the list format with a single object.

  • Multiple responses based on the options used (planner plan add)

The docs article
The MarkDown file location

  • No response (planner plan remove)

The docs article
The MarkDown file location

🔍 Example issue


📃 Issues to be picked up

The larger command groups

SPO

Teams

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions