Code formatting: Splatting input parameters before `Invoke-FabricRestMethod` calls

[NowinskiK]

There is an idea to format input parameters as splatting with hash tables.
All original code files from @tiagobalabuch use multiple lines with ` characters.
Example:

        $response = Invoke-FabricRestMethod `
            -Uri $apiEndpointUrl `
            -Method Post `
            -Body $bodyJson

New format suggested by @jpomfret :

            $apiParams = @{
                Uri    = $apiEndpointURI
                method = 'Post'
                body   = $bodyJson
            }
            $response = Invoke-FabricRestMethod @apiParams

Microsoft Learn: about_splatting

These are cosmetic changes and should not impact the current code logic.

Stats:

Method	# used
Invoke-FabricRestMethod `	154
Invoke-FabricRestMethod @ (hash splatting)	10
Invoke-FabricRestMethod - (one line)	27

[NowinskiK]

The only question I have before we start developing this change:
Do we need to use splatting for every single use of Invoke-FabricRestMethod or only for these more complex (more than 2-3 parameters)?

My recommendation would be:
a) Using a single line for a simple exec - example:

        $response = Invoke-FabricRestMethod -Uri $apiEndpointUrl -Method Get

b) Using a splatting for exec with more (>=3) input parameters - example:

        $apiParams = @{
            Uri    = $apiEndpointURI
            Method = 'Post'
            Body   = $bodyJson
        }
        $response = Invoke-FabricRestMethod @apiParams

[jpomfret]

I would vote all use splatting so it's consistent - also then we don't have to remember the rule when we're reviewing PRs.. just know it's always spatting.

[tiagobalabuch]

The key factor here is consistency. In my view, if we start mixing styles in our code, we’ll lose control over it in the long run. That’s why I strongly believe all our internal calls should always use splatting. It keeps things clean, predictable, and easier to maintain.

[NowinskiK]

OK, we have a decision then.