Skip to content
This repository was archived by the owner on Nov 26, 2024. It is now read-only.
This repository was archived by the owner on Nov 26, 2024. It is now read-only.

type provider documentation #238

Open

Description

@dsyme

I got sent a query about type provider documentation on the MSDN pages and thought I'd record my reply here for visibility:


As a meta point, we should always distinguish between

  1. Type providers as a general F# language feature
  2. The specific set of OData, SQL and WSDL type providers in FSharp.Data.TypeProviders.dll

The language feature itself is in good shape and we have an excellent set of type providers available.

The specific type providers in FSharp.Data.TypeProviders.dll were very well tested and shipped in-the-box in VS2012 but are now slowly becoming less central, and in some cases (OData) are basically obsolte Any further development on FSharp.Data.TypeProviders.dll now happens in this community project, though since they are pretty stable little development has been happening there.

Historically the MSDN documentation has always focused on the type providers in FSharp.Data.TypeProviders. We should stop doing this, and instead focus on examples using the following high-quality type providers:

Essentially we need to jettison the existing docs which refer to FSharp.Data.TypeProviders in a "privileged" way - i.e. as if these are somehow better or more important than other type providers - and use examples of the type providers above instead. (We can use either inline examples or links to examples in the relevant sites - some details of the use of the type providers may change over time)

With regard to OData v4 - I think it would be great to have a type provider for later versions of OData. However I don’t have a clear understanding of how OData has evolved since the version we support, or how widespread its use is. I think the way to start would be to open an issue in the github repo for FSharp.Data.TypeProviders. In reality I think this would however need a whole new type provider – the question is whether we can find people who need it and can write it.

Activity

  1. eriawan commented on Sep 16, 2016

    @eriawan
    Contributor

    Don Syme (@dsyme)
    I don't know exactly the widespread of OData, but afaik OData will release new version of Microsoft's ODataLIb after ODataLib v4. They even have plans for MS ODataLib to go beyond release 6, although OASIS still stays at OData v4.

    and in some cases (OData) are basically obsolte Any further development on FSharp.Data.TypeProviders.dll now happens in this community project,

    What do you mean OData are basically obsolete?

  2. dsyme commented on Sep 16, 2016

    @dsyme
    ContributorAuthor

    Eriawan Kusumawardhono (@eriawan) I mean the OData version supported by FSharp.Data.TypeProviders seems obsolete. I believe an entirely new OData type provider is needed, up-to-date with the latest version of the technology

  3. eriawan commented on Sep 17, 2016

    @eriawan
    Contributor

    Don Syme (@dsyme) could I take a stab on this OData type provider to support latest OData on existing FSharp.Data.TypeProvider?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions