Bug report: for `spo list` commands, the option `listTitle` is not enforced as string

[milanholemans]

Priority

(Medium) I'm annoyed but I'll live

Description

When trying to attach a SharePoint webhook to a library whose name is a number, the command fails.

This is because the request body looks like this:

{
  "resource": 2025,
  "notificationUrl": "https://something.example.com",
  "expirationDateTime": "2025-08-28T19:13:56.181Z"
}

The resource parameter should be a string, and not a number.

Steps to reproduce

Use list webhook add on a library whose name is a number.

Expected results

Webhook attached.

Actual results

Cannot convert a primitive value to the expected type 'Edm.String'. See the inner exception for more details.

Diagnostics

No response

CLI for Microsoft 365 version

10.4.0

nodejs version

22.14.0

Operating system (environment)

Windows

Shell

PowerShell

cli doctor

No response

Additional Info

Instead of only force typing the listTitle parameter, let's type every parameter correctly to avoid more problems.
I also suggest that we do this for every spo list command to prevent problems like these from happening.

[Adam-it]

Good find and I agree with the approach. Let's get this fixed.
Do you want to fix all spo list... commands in one go or do it as a separate follow up issue?

[milanholemans]

Good find and I agree with the approach. Let's get this fixed. Do you want to fix all spo list... commands in one go or do it as a separate follow up issue?

Since it's a quick small fix, let's check all spo list commands.