David Pedersen 2518eff0c9 Expose the operation name from juniper_rocket::GraphQLRequest (#353 )

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.

2019-05-15 07:26:40 -07:00

1.3 KiB

Raw Blame History

master

Expose the operation names from GraphQLRequest.
Compatibility with the latest juniper.

[0.2.0] 2018-12-17

Rocket updated to v0.4

Rocket integration now requires Rocket 0.4.0. This is due to changes with the way Rocket handles form parsing. Before this update, it was impossible to leverage Rocket integration with Rocket beyond 0.3.x.

Check out Rocket's Changelog for more details on the 0.4 release.

juniper_rocket [0.1.3] 2018-09-13

Add juniper-0.10.0 compatibility.

juniper_rocket [0.1.2] 2018-01-13

Changes

Rocket updated to `0.3.6`

Rocket integration now requires Rocket 0.3.6 to support building with recent Rust nightlies.

Additional information and supported nightly versions can be found in Rocket's changelog.

#125

Decoding of query params

When processing GET requests, query parameters were not properly url_decoded,

This was fixed by PR #122 by @LegNeato.

This fixed the issue #116.

1.3 KiB Raw Blame History