Catch block with 'when' clause not correctly interpreted if `or` keyword is inserted

[NoTuxNoBux]

Type narrowing with the when catch syntax only seems to be picked up correctly if the clause is relatively simple, for example:

public class Foo
{
    public async Task BarAsync()
    {
        HttpClient httpClient = new();
        HttpRequestMessage message = new();

        try
        {
            await httpClient.SendAsync(message);
        }
        catch (Exception e) when (e is HttpRequestException)
        {
            // Do something.
        }
    }
}

This correctly detects that HttpRequestException from SendAsync is handled. However:

public class Foo
{
    public async Task BarAsync()
    {
        HttpClient httpClient = new();
        HttpRequestMessage message = new();

        try
        {
            await httpClient.SendAsync(message);
        }
        catch (Exception e) when (e is HttpRequestException or JsonException)
        {
            // Do something.
        }
    }
}

This reports 'BarAsync()' may throw undocumented exception: HttpRequestException. Perhaps not all the types in the or block are scanned?

[carlreinke]

Yeah, the analyzer only recognizes expressions like ex is A || ex is B right now. It seems reasonable to also have it recognize or patterns.