Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expose the operation name from juniper_rocket::GraphQLRequest #353

Merged
merged 6 commits into from
May 15, 2019
Merged

Expose the operation name from juniper_rocket::GraphQLRequest #353

merged 6 commits into from
May 15, 2019

Commits on May 11, 2019

  1. Expose the operation name from GraphQLRequest

    Measuring the runtime of queries will only tell if there are slow
    queries. To find out which queries are slow you need the operation name.
    
    Getting the operation name was previously not possible from a Rocket
    request handler. This fixes that.
    davidpdrsn committed May 11, 2019
    Configuration menu
    Copy the full SHA
    db5eae6 View commit details
    Browse the repository at this point in the history
  2. Run cargo fmt

    davidpdrsn committed May 11, 2019
    Configuration menu
    Copy the full SHA
    3b72d87 View commit details
    Browse the repository at this point in the history
  3. Update changelog

    davidpdrsn committed May 11, 2019
    Configuration menu
    Copy the full SHA
    34ae942 View commit details
    Browse the repository at this point in the history

Commits on May 12, 2019

  1. Configuration menu
    Copy the full SHA
    c6eb3b4 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    168a763 View commit details
    Browse the repository at this point in the history

Commits on May 15, 2019

  1. Configuration menu
    Copy the full SHA
    84c410d View commit details
    Browse the repository at this point in the history