Isaac Abraham
Isaac Abraham
@giuliohome If I remember correctly, the test deliberately fails to show you how a failing test will appear in the app! But I'll double check.
Sounds good to me.
@shayanhabibi That has always been the default behaviour of .NET and shouldn't have been changed for .NET 9. My belief is that this will be rolled back / fixed in...
Would this affect behaviour at runtime using e.g. reflection over a DU?
@baronfel ok. I've found some more information on this. TLDR: If you `dotnet watch build` *from the folder of the project*, and you're using Paket, and a version of .NET...
ooooh that's interesting
I was even thinking to add that to the template anyway because it's rarely needed anyway as part of watch run.
I'm on 401 and still seeing it. I've also determined that the issue ONLY occurs with the Sdk.Web SDK, not the "regular" one.
You can also perform this operation with a single iteration of the source collection: `Seq.indexed >> Seq.maxBy snd >> fst`. However for Arrays and other eager collection types this would...
I think we've agreed to go ahead with this - can be closed once the latest template is released.