New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move important admonition from the heading Options
to Remarks
#4566
Comments
@pnp/cli-for-microsoft-365-maintainers any thoughts regarding this suggestion? |
In my opinion the whole message with Let's definitely check which docs should be updated. We should probably build a script to check this because other admonitions with other messages can also be placed in a wrong position. |
Does the remarks section show when we use the short help format? If it doesn't the moving this message means hiding it, which isn't a great idea. Perhaps it would be better to wait until we start working on adding permissions information to all commands and update it then ensuring that it will stay visible. |
We're putting these admonitions under Remarks for months now, only for old commands it's still under Options. So in fact we are already doing this now. |
While I understand your suggestion to wait until we add permissions information to all commands, I believe that the remarks section would be a better location for those comments about the commands. Many of the important comments about commands can be found in this section. Regarding the short help format, we also have a type that includes remarks. If the user wants to make sure they are fully informed about the usage of a command, it would be best practice to include this section in their help output. |
Can I work on it? |
All yours 👍 |
The idea is to move the important admonitions found under the heading
Options
to theRemarks
heading. E.g. for the commandspo cdn get
there is an important admonition under the heading options talking about permissions which feels a bit out of place there.Commands that need to be updated:
When you filter in the docs on
access the tenant admin site
you'll already find 52 commands where this change can apply.A few example commands:
spo cdn get
,spo knowledgehub get
,spo site appcatalog add
Originates from: #4521 (comment)
The text was updated successfully, but these errors were encountered: