Skip to content

Stronger signposting to GraphQL for statically-typed language users. #36774

@sleekweasel

Description

@sleekweasel

Code of Conduct

What article on docs.github.com is affected?

Because of how I reached the REST API pages, I just spent several days struggling to make OpenAPI work with Kotlin, and evaluating the third-party libraries, unaware that GraphQL was available.

it seems worth making explicit the current issues with OpenAPI for statically typed languages, and suggesting GraphQL alongside the third-party libraries, since the libraries are just a means to use GitHub and their API is an implementation detail.

What part(s) of the article would you like to see updated?

The Open API description page seems like a good place to mention the current problems with using GitlHub's polymorphic OpenAPI description with statically typed languages, and suggesting the third-party libraries and/or GraphQL as alternatives.

The libraries page also seems like a good place to mention GraphQL in the 'Official GitHub Library' section.

Additional information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    contentThis issue or pull request belongs to the Docs Content teamtriageDo not begin working on this issue until triaged by the team

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions