VS UI analysis is sensitive to type parameter ordering

[mmesdag]

I have a component that takes two type parameters, one of which is constrained using the second as a type parameter of the constraint. If, in the component usage on a razor component, the type parameters are specified in the opposite order that they are on the component where they are used, VS shows an error in the UI, but builds correctly. I see no warnings or errors in the build, Rider doesn't complain, and the code works correctly, so seems to me like a VS tooling issue.

Changing the order of the type params so that they match what is defined in the component fixes the error

This only happens if the component has an @bind applied as well (as far as I can tell). A minimal repro (based on the .net 8 blazor web app template) is available here: https://github.com/mmesdag/RazorTypeParameterOrderingError.

Component with type params:

@typeparam TService where TService : IInterfaceConstraint<TKey>
@typeparam TKey

@code {
    [Parameter]
    public required TKey? Value { get; set; }

    [Parameter]
    public EventCallback<TKey> ValueChanged { get; set; }
}

Type param constraint:

public interface IInterfaceConstraint<T>
{
}

Type used in component usage

public interface IComposedInterface : IInterfaceConstraint<string>
{
}