juniper/juniper_iron/Cargo.toml

[package]
name = "juniper_iron"
version = "0.2.0"
authors = [
    "Magnus Hallin <mhallin@fastmail.com>",
    "Christoph Herzog <chris@theduke.at>",
]
description = "Iron integration for juniper"
license = "BSD-2-Clause"
documentation = "https://docs.rs/juniper_iron"
repository = "https://github.com/graphql-rust/juniper"

[dependencies]
serde = { version = "1.0.2" }
serde_json = { version = "1.0.2" }
serde_derive = { version = "1.0.2" }
juniper = { version = ">=0.9, 0.10.0", path = "../juniper" }

urlencoded = { version = ">= 0.5, < 0.7" }
iron = ">= 0.5, < 0.7"

[dev-dependencies]
iron-test = "0.6"
router = "0.6"
mount = "0.4"
logger = "0.4"
url = "1.7.1"

[dev-dependencies.juniper]
version = "0.10.0"
features = ["expose-test-schema", "serde_json"]
path = "../juniper"
Move juniper_iron crate back into the main repo. This is done for a lower maintainance burden and combined testing. 2017-12-02 08:55:29 -06:00			`[package]`
			`name = "juniper_iron"`
0.10.0 release (#236) * Bump` juniper`, `juniper_codegen`, and `juniper_tests` versions. * Bump integration crate requirements to include 0.10.0. `juniper_iron` gets a semver breaking version as it has a breaking change but `juniper_iron` does not. * Move `juniper_rocket` changelog into one file. This aligns with `juniper_iron` and will be easier to automate in the future. * Let `juniper_warp` and `juniper_hyper` use `0.9.x` versions of Juniper. They don't rely on anything in 0.10.0 so don't require it. 2018-09-13 11:13:31 -05:00			`version = "0.2.0"`
Bump to 0.9.1 and fix up Cargo.toml files 2017-12-03 11:33:40 -06:00			`authors = [`
			`"Magnus Hallin <mhallin@fastmail.com>",`
			`"Christoph Herzog <chris@theduke.at>",`
			`]`
Move juniper_iron crate back into the main repo. This is done for a lower maintainance burden and combined testing. 2017-12-02 08:55:29 -06:00			`description = "Iron integration for juniper"`
			`license = "BSD-2-Clause"`
			`documentation = "https://docs.rs/juniper_iron"`
Fix repository links in iron/rocket Cargo.toml 2017-12-03 06:12:45 -06:00			`repository = "https://github.com/graphql-rust/juniper"`
Move juniper_iron crate back into the main repo. This is done for a lower maintainance burden and combined testing. 2017-12-02 08:55:29 -06:00
			`[dependencies]`
Final readme and cargo.toml fixups 2017-12-03 08:14:23 -06:00			`serde = { version = "1.0.2" }`
Move juniper_iron crate back into the main repo. This is done for a lower maintainance burden and combined testing. 2017-12-02 08:55:29 -06:00			`serde_json = { version = "1.0.2" }`
Handle an array of GraphQL queries (#171) 2018-06-07 19:44:30 -05:00			`serde_derive = { version = "1.0.2" }`
0.10.0 release (#236) * Bump` juniper`, `juniper_codegen`, and `juniper_tests` versions. * Bump integration crate requirements to include 0.10.0. `juniper_iron` gets a semver breaking version as it has a breaking change but `juniper_iron` does not. * Move `juniper_rocket` changelog into one file. This aligns with `juniper_iron` and will be easier to automate in the future. * Let `juniper_warp` and `juniper_hyper` use `0.9.x` versions of Juniper. They don't rely on anything in 0.10.0 so don't require it. 2018-09-13 11:13:31 -05:00			`juniper = { version = ">=0.9, 0.10.0", path = "../juniper" }`
Fix up Cargo.toml files and documentation. 2017-12-02 09:09:08 -06:00
(iron) Update to iron 0.6 * Allow both iron 0.5 and 0.6 * Allow both urlencoded 0.5 and 0.6 2018-02-05 01:40:54 -06:00			`urlencoded = { version = ">= 0.5, < 0.7" }`
			`iron = ">= 0.5, < 0.7"`
Move juniper_iron crate back into the main repo. This is done for a lower maintainance burden and combined testing. 2017-12-02 08:55:29 -06:00
			`[dev-dependencies]`
(iron) Update to iron 0.6 * Allow both iron 0.5 and 0.6 * Allow both urlencoded 0.5 and 0.6 2018-02-05 01:40:54 -06:00			`iron-test = "0.6"`
			`router = "0.6"`
			`mount = "0.4"`
			`logger = "0.4"`
Escape urls in iron integration tests (#208) It appears with newer 0.10.x hyper it no longer takes "{" or "}" in the query string unescaped. When I tried to set `juniper_iron` to an older hyper it complained that it couldn't resolve due to `juniper_rocket` needing a newer version. This was the path of least resistance. Note that we are still testing the same thing, this change is needed as a consequence of how `iron_test` creates mock requests. Fixes https://github.com/graphql-rust/juniper/issues/206 2018-07-12 20:34:37 -05:00			`url = "1.7.1"`
Fix up Cargo.toml files and documentation. 2017-12-02 09:09:08 -06:00
			`[dev-dependencies.juniper]`
0.10.0 release (#236) * Bump` juniper`, `juniper_codegen`, and `juniper_tests` versions. * Bump integration crate requirements to include 0.10.0. `juniper_iron` gets a semver breaking version as it has a breaking change but `juniper_iron` does not. * Move `juniper_rocket` changelog into one file. This aligns with `juniper_iron` and will be easier to automate in the future. * Let `juniper_warp` and `juniper_hyper` use `0.9.x` versions of Juniper. They don't rely on anything in 0.10.0 so don't require it. 2018-09-13 11:13:31 -05:00			`version = "0.10.0"`
Fix up Cargo.toml files and documentation. 2017-12-02 09:09:08 -06:00			`features = ["expose-test-schema", "serde_json"]`
			`path = "../juniper"`