We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
(Low) Something is a little off
m365 spo listitem list -h shows:
-p, --pageSize [pageSize] Number of list items to return. Specify camlQuery or pageSize but not both. The default value is 5000.
But in fact short option for page size is: -s
m365 spo listitem list -u <> -t <> -p 1
Return only one list item
Returns all list items
No response
v6.7.0
v19.4.0
Linux
bash
It should work according help page or the help should be changed.
The text was updated successfully, but these errors were encountered:
Good catch @dojcsakj! Would you like to fix this one, or should we open it up for the community?
Sorry, something went wrong.
I'm happy to do that. :)
Should I modify the help text or the short option?
I'm happy to do that. :) Should I modify the help text or the short option?
Let's update the docs, else it would be a breaking change. Thank you for your help!
7023bfd
dojcsakj
Successfully merging a pull request may close this issue.
Priority
(Low) Something is a little off
Description
m365 spo listitem list -h shows:
-p, --pageSize [pageSize]
Number of list items to return. Specify camlQuery or pageSize but not both. The default value is 5000.
But in fact short option for page size is: -s
Steps to reproduce
m365 spo listitem list -u <> -t <> -p 1
Expected results
Return only one list item
Actual results
Returns all list items
Diagnostics
No response
CLI for Microsoft 365 version
v6.7.0
nodejs version
v19.4.0
Operating system (environment)
Linux
Shell
bash
cli doctor
No response
Additional Info
It should work according help page or the help should be changed.
The text was updated successfully, but these errors were encountered: