PSAvoidUsingUserNameAndPassWordParams should not fire if function/cmdlet has a credential parameter

[splatteredbits]

My module, Carbon, has some functions written before I knew what I was doing that take in UserName/Password instead of a credential. I plan on adding credential parameters, but because of backwards-comparability, I have to leave the original UserName/Password parameters in place.

I'd like PSAvoidUsingUserNameAndPassWordParams to pass if a function has a credential parameter in addition to UserName/Password.

[nobodyguy]

My 2 cents: I don't think this rule should have error severity.

[kilasuit]

I have a function that has the ability to input either a Credential Object or Username and Password to give the end users more flexibility especially as this could be for some the initial use of PowerShell

I agree with @splatteredbits that this should pass if the function has Credential & Username and Password parameters but should flag up if there is no Credential parameter

[kilasuit]

Should this rule purely be informational - i.e to inform that the user that there is are better ways and that they should be investigating those methods instead.

[quoctruong]

Fixed with #391 and #394