Get-FormatData quietly ignores non-existing type-name arguments

Steps to reproduce

Get-FormatData NoSuch.Type.Exists.Or.IsLoaded

Expected behavior

An error that indicates that the type does not exist (in the current session).

Actual behavior

A quiet no-op. No output, $? reports $True.

Environment data

PowerShell Core v6.0.0-beta.3 on macOS 10.12.5
PowerShell Core v6.0.0-beta.3 on Ubuntu 16.04.1 LTS
PowerShell Core v6.0.0-beta.3 on Microsoft Windows 10 Pro (64-bit; v10.0.14393)
Windows PowerShell v5.1.15063.413 on Microsoft Windows 10 Pro (64-bit; v10.0.15063)

[Jaykul]

HANG ON … This is a breaking change to the function!!!

Does -ErrorAction SilentlyContinue work, or are you now forcing everyone to wrap this in a try/catch block?

I understand the desire to have this produce an error, but we can’t make existing commands throw exceptions in use cases that used to just return nothing.

You’re breaking every instance of existing code that looks like this, right?

if(!(Get-FormatData $Type)) {
   Update-FormatData -TypeName $Type ...
}

[SteveL-MSFT]

@faraazahmad consider it yours! Thanks!