Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

The -InformationAction common parameter alias is inconsistent with other stream common parameter aliases

See original GitHub issue

All common parameters that have to do with streams follow a two-letter alias format (first letter of the stream name followed by the first letter of “Action” or “Variable”). In fact, -InformationVariable has an alias of iv. So why does -InformationAction break the mold with an alias of infa instead of simply using ia as an alias? I couldn’t find any competing ia alias in common parameters.

This issue should be addressed by adding ia as a secondary alias for the -InformationAction common parameter.

Issue Analytics

State:
Created 4 years ago
Reactions:2
Comments:8 (3 by maintainers)

Top GitHub Comments

1reaction

iSazonovcommented, Oct 2, 2019

@KirkMunro I suggest reword the issue as “proposal” (or open new issue) - in the case I hope we will get a progress faster. (I don’t see reasons why we can not add the new aliases)

0reactions

iSazonovcommented, Oct 10, 2019

Reference to PowerShell Committee conclution https://github.com/PowerShell/PowerShell/pull/10703#issuecomment-540231767

Top Results From Across the Web

about CommonParameters - PowerShell

The following list displays the common parameters. Their aliases are listed in parentheses. Debug (db); ErrorAction (ea); ErrorVariable (ev) ...

1. The PowerShell Interactive Shell

Aliases let you refer to common commands by a name that you choose. Personal profile scripts let you automatically define aliases, functions, variables,...

Setting new alias in PowerShell getting error

1 Answer. Aliases in PowerShell cannot have parameters as part of the alias - that is, you can make touch an alias for...

PowerShell basics - Notes from a DevSecOps consultant

Another example of aliases in PowerShell is the common mapping of both older command prompt commands and BASH commands to PowerShell cmdlets.

Why don't my functions have common parameters?

I'm trying to write some code that requires examining the functions metadata and processes some other data based on the command's parameters. In ......