Parameter name consistency

[SQLDBAWithABeard]

Problem description

Just like in dbatools unless required, the parameter for Name should be Name when being used with the resource

for example

Get-FabricWorkspace -Name
Get-FabricWorkspace -id

Get-FabricSqlDatabase -Name fabbydatabase -WorkspaceName worky

also linked to #26

Verbose logs

no logs

How to reproduce

suggestion

Expected behavior

Use the right Paramter naming structure

Current behavior

the name is -ResourceName everywhere - this will need to be aliased to avoid breaking changes

Suggested solution

alter the parameters for Name

Operating system you are running FabricTools on

The Cloud

PowerShell version and build the target node is running

Yes

Module version used

latest

[NowinskiK]

Good idea @SQLDBAWithABeard.
I agree that we could add aliases for Names and Ids, but do not remove any existing parameters' names.
Most of the code comes from @tiagobalabuch, and it's at least consistent across (which is good), and I'd like to hear his opinion about it before anyone start working on this.
There are also some exceptions, where two/more Ids for input parameters needed:

function Assign-FabricWorkspaceCapacity {
    [CmdletBinding()]
    param (
        [Parameter(Mandatory = $true)]
        [ValidateNotNullOrEmpty()]
        [string]$WorkspaceId,

        [Parameter(Mandatory = $true)]
        [ValidateNotNullOrEmpty()]
        [string]$CapacityId
    )

[SQLDBAWithABeard]

Yup, that's another example, just like the SqlDatabase one where things need to be different.

[tiagobalabuch]

@NowinskiK I’m okay with adding aliases for the parameters, even though I don’t think it adds much clarity. You made a good point with the example where there are two IDs