Adding check for empty string as well as null

[reubenmiller]

When using the -Credentials parameter when calling Invoke-PSDepend for dependencies that don't require credentials, would result in the erroneous warning WARNING: No credential found for the specified name . Was the dependency misconfigured?

Example

Invoke-PSDepend -Path "./depends.psd1" -Install -Import -Credentials @{
  "repo1WithCredential" = (Get-Credential)
}

File depends.psd1

@{
    "PSModule1" = @{
        
        "Name"           = "PSModule1"
        "Version"        = "1.0.0"
        "DependencyType" = "PSGalleryModule"
        "Credential"     = "repo1WithCredential"
        "Parameters"     = @{
            "Repository" = "repo1WithCredential"
        }
    }
    "PSModule2" = @{
        "Name"           = "PSModule2"
        "Version"        = "2.1.0"
        "DependencyType" = "PSGalleryModule"
        "Parameters"     = @{
            "Repository" = "repo2WithoutCredential"
        }

Would generate the warning when processing the PSModule2 dependency.

WARNING: No credential found for the specified name . Was the dependency misconfigured?

Fix

The -Name parameter in Resolve-Credential is cast from $null to an empty string "". So now both null and an empty string are checked.

[reubenmiller]

Resolves $null credential issue referenced at the end of #94

[Copilot]

Pull request overview

This PR aims to prevent an erroneous warning when Invoke-PSDepend is called with -Credentials but a given dependency does not specify a credential name (or the name becomes an empty string due to [string] casting).

Changes:

• Updates Resolve-Credential to treat empty string credential names the same as $null (via [string]::IsNullOrEmpty()), preventing spurious warnings.
• Modifies a brace near the end of Parse-Dependency (currently resulting in unbalanced braces / incorrect scoping in the updated file).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.