ConvertFrom-ClearlyDefinedCoordinates only accepted [string] input, but Get-ClearlyDefinedData returns the raw ClearlyDefined API response whose coordinates property is a deserialized PSCustomObject — not a string. PowerShell coerced the object to "@{type=nuget; provider=nuget; name=Markdig.Signed; revision=1.0.0}", which split by / produced no useful parts, causing Start-ClearlyDefinedHarvest to fail [ValidateSet('nuget')] on PackageType.

Changes

• tools/clearlyDefined/src/ClearlyDefined/ClearlyDefined.psm1: Removed [string] type constraint from ConvertFrom-ClearlyDefinedCoordinates and added branch logic to handle both input forms:
  • String (e.g. from failed API calls where coordinates is stored as "nuget/nuget/-/Name/Version"): splits by / as before
  • Object (PSCustomObject from a successful API response): extracts type, provider, namespace, name, revision properties directly

# Before: only handled string input
[string] $Coordinates
$parts = $Coordinates.Split('/')

# After: handles both string and object (API response) input
$Coordinates  # untyped
if ($Coordinates -is [string]) {
    $parts = $Coordinates.Split('/')
    [PSCustomObject]@{ type = $parts[0]; ... }
} else {
    [PSCustomObject]@{ type = $Coordinates.type; name = $Coordinates.name; ... }
}

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.