yume/juniper
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
juniper/juniper_hyper/CHANGELOG.md
Kai Ren aedb2d1eb4
Support "Content-Type: application/graphql" (#426) (#654) 
* Support 'application/graphql' POST requests for 'juniper_warp'

* Add integration tests for 'application/graphql' POST requests and revive HttpIntegration test suite for 'juniper_warp'

* Support 'application/graphql' POST requests for 'juniper_hyper' and run its tests for both sync and async versions

* Run integration tests for both sync and async versions of 'juniper_warp' and update its CHANGELOG

* Support 'application/graphql' POST requests for 'juniper_iron'

* Fix 'application/graphql' POST requests support for 'juniper_actix'

* Support 'application/graphql' POST requests in 'juniper_rocket' and 'juniper_rocket_async'

* Upd juniper's CHANGELOG
2020-05-08 06:00:49 -10:00

1.5 KiB
Raw Blame History

master

  • Compatibility with the latest juniper.

Breaking Changes

  • juniper_hyper::graphiql now requires a second parameter for subscriptions.
  • juniper_hyper::graphql now executes the schema asynchronously. For blocking synchronous execution consider juniper_hyper::graphql_sync for use.
  • 400 Bad Request is now returned if POST HTTP request contains no or invalid Content-Type header.

[0.5.2] 2019-12-16

  • Compatibility with the latest juniper.

[0.5.1] 2019-10-24

  • Compatibility with the latest juniper.

[0.5.0] 2019-09-29

  • Compatibility with the latest juniper.

[0.4.1] 2019-07-29

  • Compatibility with the latest juniper.

[0.4.0] 2019-07-19

  • Compatibility with the latest juniper.

[0.3.0] 2019-05-16

  • Compatibility with the latest juniper.

0.2.0 [2018-12-18]

Breaking changes

  • The tokio threadpool managed by hyper is now used for executing GraphQL operations as well. Previously a separate threadpool from futures_cpupool was required.

    #256