Ben Collins

I recently had this problem with SQLProvider (https://github.com/fsprojects/SQLProvider/issues/645), and relying on MSBuild and the `net` FSAC backend in ionide was enough to muddle through. However, according to Phillip Carter (https://github.com/dotnet/fsharp/issues/3303#issuecomment-499977412),...

@amwx thanks for the tip. That seems to have done it. Any idea why this is necessary?

@mabasic Thank you so much for powering through this writing up this thorough explanation and resource list. This has been tremendously helpful to me working on the same thing!

Hmm; after digging around here: https://docs.microsoft.com/en-us/azure/azure-functions/functions-versions#migrating-from-2x-to-3x it seems I should have been using the v3 tooling, which was only available via chocolatey by specifying the version number, like this: `choco...

I agree. I would really not like to either - roll my own validation library - take a dependency on jQuery, which I have been fastidiously avoiding, just for this

I added a new solution file just to make it a little bit nicer for me as I make changes incrementally. Eventually everything will be updated and I'll remove `dotnet-updates.sln`.

Sure, I don't mind. This is what I generated using apollo against the Shopify API (documented here: https://help.shopify.com/en/api/graphql-admin-api). [shopify_schema.zip](https://github.com/fsprojects/FSharp.Data.GraphQL/files/3740895/shopify_schema.zip) The mutation above is just cruft, really. The issue manifests before...

I think this must have been caused by the particular json schema that was generated by apollo. I generated schema with a different tool (`graphql schema` with the graphql cli)...

Another bit: I generated a json schema using the introspection query from the README, and the provider seems happy enough with that. I don't know the differences between the produced...

This seems fine to me 👍 (with the caveat that I can't fully visualize what everything would look like just from the settings).