@bilkusg Sorry for the delay. We've decided to rewrite the GraphQL provider. The plan is to support Fable in the near future. You can preview the work in #179.

Any feedback is appreciated!

Hi, should the latest beta work with Fable? I believe the source files are missing from the nuget package.

Is the TypeProvider an Erasure one?

Hi @nojaf,

We haven't added support for Fable in the latest type provider redesign. @alfonsogarciacaro wrote the first Fable integration, so he knew what he was doing w.r.t. Fable. Do you know if the mechanism we were using in the old TP is still valid?

Thanks,
John

What is the status of the type provider with Fable?

The status is : not working with Fable since 2.0.
AFAIK, there is only one provider for current fable and it is JsonProvider from @alfonsogarciacaro
The official doc still states that is working with fable client-side, perhaps update?

Providers work with latest version of Fable but they cannot use the parts of the BCL that are not supported by Fable. You can find some providers compatible with Fable by typing "provider" here: https://fable.io/community/

Recently I have a published a different solution for Fable called Snowflaqe. It is a dotnet CLI tool that code-generates a Fable (or F#) GraphQL client project based on the schema and input query files. The tool also performs validation and partial type-checking against the input queries.

Recently I have a published a different solution for Fable called Snowflaqe. It is a dotnet CLI tool that code-generates a Fable (or F#) GraphQL client project based on the schema and input query files. The tool also performs validation and partial type-checking against the input queries.

Interesting! Why code generation over a Type Provider?

Thanks @Zaid-Ajaj that's a very convenient solution, but ultimately someone will have to get its hands dirty and properly code the TP for fable 2.* ... I would like to do it, no guarantee.

Interesting! Why code generation over a Type Provider?

@njlr Type providers are hard to write, hard to debug and have limitations in which types you can output where you can't generate records or unions. This is very important because AFAIK records are required for proper serialization and deserialization of JSON data given the limited Reflection support on classes for Fable.

but ultimately someone will have to get its hands dirty and properly code the TP for fable 2.* ... I would like to do it, no guarantee.

@fradav Please do! To be honest I personally wouldn't know how the runtime code should behave in Fable 2.0 with classes, let alone generate that via a type provider. For now it is good to have at least one working solution for Fable developers. I have been happily using it myself at work and we are quite enjoying it so far 😄