* Use mdbook for building the book
* Update book config
* Update book hierarchy to work properly with mdbook
This necessitated adding place-holder index pages
since mdbook does not suppoert stand-alon menu items
* Update tests to use 2018 edition
* Fix various compilation errors in the tests
The literal value according to the standard is INLINE_FRAGMENT,
not INLINE_SPREAD.
This oversight leads to invalid introspection schemas and trips up
third party tools.
Currently, custom derives inside the main juniper crate are supported by
an ugly hack using the __juniper_use_everything macro.
This commit adds new custom derive variants that are for
main juniper crate internal use only (GraphQL{Enum,InputObject}Internal.
All custom derives inside the juniper crate are refactored to use the
new '*Internal' derives.
This allows us to
* remove the use_everything macro,
* simplify the generated code for custom derives
* support the Rust 2018 edition
This commit refactors the macros to use the $crate::inner_macro
trick instead of local_inner_macros.
This is possible since we only support rust 1.30 as a minimum version.
(the $crate:: method only works on 1.30+).
With this change, the wrapper helper macros for std macros can also
be removed.
Partially fixes https://github.com/graphql-rust/juniper/issues/248.
* Install `cargo-release`. (currently need a patched one with https://github.com/sunng87/cargo-release/pull/74)
* Run `cargo make release-dry-run` to do a dry run of a release
* Run `cargo make release` to do a minor versioned release of every crate
* Run `cargo make release-patch` to do a patch release of every crate
To only release one crate:
* Change directories into the desired crate
* Point `cargo-make` to the workspace-level Makefile when running a command. For example, `cargo make --makefile ../Makefile.toml release-dry-run`.
From the workspace root, run `cargo
Path handling changed in Rocket 0.4 and this commit updates the way
those paths are handled. It adds an implementation of the
`FromFormValue` trait to the `GraphQLRequest` object. It also changes
the documentation to use the multi-segment query string syntax.
All existing tests pass as expected.
This isn't needed, as examples by default are built when the
containing crate is tested.
I also confirmed that `cargo run --example warp_server` still works.
* Build wasm32-unknown-unknown in CI (#218)
`cargo check --wasm32-unknown-unknown` is sufficient to demonstrate that the
`juniper` and `juniper_codegen` crates can compile for WebAssembly, which should
help avoid accidental regressions.
