ScottKane

Shouldn't this have been done by now according to the 2 year old roadmap? https://github.com/grpc/grpc-web/blob/master/doc/streaming-roadmap.md

For my Blazor WASM app initial loading is taking 5-10 seconds which is bad enough but on click events from buttons are taking around 2 seconds to fire when accessing...

@danroth27 I opened https://github.com/dotnet/aspnetcore/issues/43090 for this, I'm currently rebuilding the client from scratch to figure at at what point the performance dies. So far the only thing I can point...

I disagree, if this is the case we should be able to override the default to false. I don't understand why a form would be assumed to be valid without...

The user experience of getting incremental errors as you tab past required fields is nice but they shouldn't be able to submit the form at all. If the validator was...

By all means if you can explain to me why there is any benefit in making the assumption that a form that hasn't been validated is better than just validating...

As we're working with entities I would go with: ```c# public interface IEntity { } public interface IEntity : IEntity { public TId Id { get; set; } } ```...

Yeah I would agree this kind of falls into repository pattern territory

This is a bit awkward though as the more I think about it, the less I think validation attributes belong in domain models. They are better suited at a dto...

Is this planned to just facilitate adding `Authorize` attributes to specific endpoints, or do you think we could also provide a default JWT based authentication flow (supporting refresh tokens etc)...