LGTM to me 👍👍.
I would only use id instead of uniqueId

@pnp/cli-for-microsoft-365-maintainers any other feed on that?

We'll need to add a few additional remarks for this command it seems. If I read the docs right, it stated that the model needs to be removed from every library before you can delete it. So that seems like something we should best notify the users about in the docs. First, I thought we needed to also specify each library where it is applied before we can delete it but it seems that there is an "easy" endpoint we can call to get all the needed information: https://learn.microsoft.com/en-us/sharepoint/dev/apis/syntex/rest-getmodelandlibraryinfo. With this result, we can make sure that the model is removed from all libraries and then delete it.

• Also, let's replace all the occurrences of Syntex with SharePoint Premium. 😉
• One smaller detail, in your examples, there are two spaces between your command and the first option. remove --siteUrl
• The section default properties can also be removed as we won't need it here.

hi @Jwaegebaert thank you for all comments. I have added the Remark section to the command, I hope that it will be ok.

Awesome, nothing further to add. Do you want to work on it or open it up?

I suggest we reconsider naming. Since we use spe to indicate SharePoint Embedded, shouldn't we use spp to indicate SharePoint Premium? Premium is not a feature set, it's a licensing SKU, right? I suggest that we treat it consistently as a product/workload.

@Jwaegebaert yes I can take it :)
@waldekmastylkarz let me copy your comment to the place where we had the discussion about the naming.

I agree with @waldekmastykarz. Great idea!

@mkm17 perfect 🤩.
lets 🚀 this