New command: list custom actions

List all custom actions at the given scope.

• command: spo customaction list --url|-u <url> --scope|-s [scope]
• url of the site/web to retrieve custom actions for
• scope to retrieve custom actions for. Allowed values Site|Web|All. Default All
• requires connection to a SharePoint site

Decide which properties should be retrieved. Given that there can be many custom action defined at the given scope, this command should ideally include the minimum set of properties. To get all properties for the given custom action, users can run the spo customaction get command.

More information at https://msdn.microsoft.com/en-us/pnp_powershell/getpnpcustomaction

[VelinGeorgiev]

Initially my thoughts were to have 5+ columns as well, but now I would suggest to keep it simple at that early stage. --details adds more logic and skip of the null valued properties also would add even more logic in the command. I would prefer, we focus on the commands quantity over prettifying the output suggested by @andrewconnell.

I can implement it as you wish and it is not a problem, I would rather prefer to see similar output as what we have on the PnP powershell command (small table) because it might be hard to read in a 800x600 console if we go with 5+ columns. Then we can very quickly execute spo customaction get --id for the action we are interested in to get more details.

[damsleth]

Following the PnP PowerShell cmdlet pattern with a table layout I agree it’s best to keep the # of columns to a minimum. The (pretty neat, actually) --debug switch really covers all verbosity requirements.