i think this type provider and this issue deserve community attention
i will try to get to know how to develop a very simple test type provider in the meantime, as for know i don’t have enough knowledge to try “fix it” myself but if anyone can help on that one. this would be great
I am pushing very hard to convince my colleagues and my company to use F# and to transition from C# or use side-ways when possible , and this is awesome, the community is full of amazing people and resources. I really love it.
A major barrier for me is showing the usage of type providers (apart from standard ones in FSharp.Data),
I do see that .net/microsoft/xamarin/jetbrains F# communities in general are not really committed to this area, or at least it doesn’t show.
it looks like type providers are way cooler than most people realize. In my view they clearly make F# stand out as a language in a very sharp way.
I see type providers especially useful for enterprise development as well as fast prototyping (and fun),
though many times they do not seem extensively tested or they do not seem a major focus of the language (whereas it might be its winning point in the long run?).
In my view e.g. SQL type providers (both the one with dbcontext and sqlCommandProvider) and OpenApi(Swagger) type provider should be the stallions of F# marketing to C# developers. I believe once devs really see them in action, they cannot deny the true infinite F# power e.g.