Ryan Coy

This isn't a Bolero issue - this is a usercode issue that's cropping up at the JSON (de)serialization layer. You can't deserialize interface types because they're not concrete implementations of...

But that forces a dependency on FSharp.Data, which is both huge and unnecessary. Bolero already has opinions on JSON serialization - via FSharp.SystemTextJson. Nothing is blocking individual consumers of Bolero...

Calling the Javascript would be done via JSInterop - I believe it's IJSRuntime that needs to be injected into your ProgramComponent. In terms of recognizing that a user is authenticated,...

This is presently resolved in source as of [827f77ca8d9f969b6d75fb7230b2fb89ae1263a8](https://github.com/ionide/Fornax/commit/827f77ca8d9f969b6d75fb7230b2fb89ae1263a8) - so it should get picked up in the next release.

@dsyme Updated, but I'm curious about the concept of `preference` here - in the case that we're defining an extension method on top of an intrinsic property of a function-type,...

> Yes, this would be a breaking change for this case. I doubt it occurs in practice (why would anyone have defined the unusable extension method?), but we could code...

I must be conflating and misusing some terminology somewhere here 😅 Here's the simplest interactive/REPL-able side-by-side repro of the problem, in the wild: In C#, this functions: ```cs #r "nuget:...

Yep, that's a reasonable description of what's going on in the typechecker when this throw the error. And we do 'know' towards the top of this process that the next...

> This feature is supposed to create an alternative to: > > ```fsharp > //Every C# dev knows this pain: > var f = new Foo(); > f.X = 1;...

Of course: