Skip to content

Give names to all our GraphQL queries #997

Closed

Description

@mislav

To have better visibility into our API traffic, the different types of our GraphQL queries should each have distinct names.

TODO:

  • explore how we can do this for queries using shurcooL/githubv4

/cc @billygriffin

Activity

  1. billygriffin commented on Jun 24, 2020

    @billygriffin
    Contributor

    @mislav I think you said doing this for a large percentage of our queries would be relatively trivial and into an upcoming release, but I wanted to see what you're thinking for this overall.

    cc: @ampinsk

  2. mislav commented on Jun 25, 2020

    @mislav
    ContributorAuthor

    For the majority of our queries we can add this easily, but for the ones using githubv4 library, we will need to fork the library because, when I looked into it, it did not offer any mechanism to generate named queries.

    All in all I think this would be ~2 days of work that I think we could fit in the next release!

  3. rnystrom commented on Jun 25, 2020

    @rnystrom

    Chiming in to offer help building a pipeline + dashboard once we have names. I'll basically copy this mobile actions mapping for CLI.

    Are yal using the REST API too? We can just map based on the path, but good to if we'll need to look from multiple sources.

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

Metadata

Metadata

Assignees

Labels

tech-debtA chore that addresses technical debt

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions