Passing jsons in POST/PATCH requests is not administrator friendly

Is your feature request related to a problem? Please describe the problem.

We have a set of cloud printing APIs exposed in Microsoft Graph.

Currently Graph generated powershell requires users to provide inputs for POST/PATCH requests as json, which is developer friendly but not admin friendly.
e.g. following is the comparison of Universal Print operations using custom Universal Print powershell module and Graph generated powershell module for sharing printer.

Universal Print powershell module:
New-UPPrinterShare -PrinterId "cdd44642-8fc3-4f55-bce2-d6d8069b40f2" -ShareName "First Floor Printer"

Graph generated powershell module:
$params = @{ DisplayName = "ShareName" AllowAllUsers = $false Printer@odata.bind = https://graph.microsoft.com/v1.0/print/printers/{printerId} }
New-MgPrintShare -BodyParameter $params

Hence, requesting Graph powershell team to address this concern.
This is blocking our team from deprecating Universal Print powershell module in favor of Graph generated powershell module.

Describe the solution you'd like.

Admins can provide required info as named parameters instead of jsons. e.g. consider Universal Print custom powershell module command for sharing printer:

New-UPPrinterShare -PrinterId "cdd44642-8fc3-4f55-bce2-d6d8069b40f2" -ShareName "First Floor Printer"

Additional context?

No response

No file, test, or entry point is identified. Start by reviewing the POST/PATCH examples for Universal Print and Graph-generated PowerShell cmdlets, then determine the generation scope needed to expose inputs as named parameters; done means administrators can use named parameters instead of JSON body parameters.