Naming convention for site collection commands

What do you think would be the logical naming convention for working with site collections in the CLI?

Today, we have classic and modern sites. While they’re both site collections, you work with them differently (different API, parameters and shape). In PnP PowerShell there are two sets of cmdlets: PnPTenantSite for classic sites and PnPSite for modern sites. What would be the logical naming convention to use in the CLI?

1. spo site <action> for modern and spo site classic <action> for classic sites (since modern sites are likely the way forward it would be better to not include modern in the command name, and instead explicitly denote classic sites)
2. spo modernsite <action> and spo classicsite <action>
3. spo site modern <action> and spo site classic <action> to explicitly denote type of site you want to be working with
4. spo site <action> --type Modern|Classic for both classic and modern. Distinction between classic in modern is done inside each command. This would introduce higher complexity of all commands because they would have to handle two types of sites, including validating required options which are different depending on the type of site you’re working with. Preferably we shouldn’t choose this approach but maybe you have good arguments for doing it.

Any other naming conventions? Which one has your preference and why? @VelinGeorgiev @estruyf @andrewconnell @wictorwilen

[andrewconnell]

Correct… I think to go in line with what most CLIs do I’d expect to see something more like option 4:

spo site list --type classic
spo site list --type modern
# the following is the same as the modern option above
spo site list

[benstegink]

I vote for #1 as well