• besides the usual naming and support for site-relative URL
• why don't we want to use retainInheritedPermissions as well?
• any reason why in the scope we don't allow the user option? seems to be supported as well
  
• the default response it return has complex object

{
  "id": "123ABC",
  "roles": ["write"],
  "link": {
    "type": "view",
    "scope": "anonymous",
    "webUrl": "https://1drv.ms/A6913278E564460AA616C71B28AD6EB6",
    "application": {
      "id": "1234",
      "displayName": "Sample Application"
    },
  },
  "hasPassword": true
}

which is a shame as we will lose a lot of useful info in the text and csv output mode. I wonder if it would be possible to customize the response for this mode to also print out this info 🤔 @pnp/cli-for-microsoft-365-maintainers any comments on that.

besides the above I don't currently see anything else

• any reason why in the scope we don't allow the user option? seems to be supported as well

It is supported now indeed. I'll add this to the scope, however this requires another option for the recipients.

Thanks for the feedback @Adam-it. I have implemented all the suggestions.
Regarding the output, it's hard for me to judge.

@milanholemans, if I recall, we talked a while ago about formatting nested properties for the text output. We ended up creating a custom property (#5900). What was the decision on handling these situations moving forward?

I think for the time being, it's ok to manipulate the result object for text etc.
But in the future there will probably another way of working which we can't do right now.

in this case, I would flatten the complex to return also type, scope, webUrl and other properties

Can I work on this?

Definitely!