GraphQL server library for Rust
Find a file
2020-01-21 09:22:14 -08:00
.github/ISSUE_TEMPLATE Update issue templates 2019-02-03 17:44:16 +01:00
_build ci: Fix used rust version 2019-11-16 03:39:36 +01:00
assets/logo Logo: move to /assets and add to readme. 2017-09-23 19:13:13 +02:00
benches Rebase onto master 2019-11-06 11:45:19 +03:00
docs/book Add async to doc tests 2020-01-21 08:38:13 -08:00
examples/warp_async Rename object proc macro to graphql_object 2019-11-16 02:57:48 +01:00
integration_tests Add async feature flag 2020-01-21 08:04:08 -08:00
juniper Fix formatting 2020-01-20 23:29:29 -08:00
juniper_benchmarks Add empty changelog to make release dry-run work 2020-01-21 08:28:31 -08:00
juniper_codegen Break dep cycle again 2020-01-21 07:53:36 -08:00
juniper_hyper Only run async tests on master for crates that require master 2020-01-21 09:22:14 -08:00
juniper_iron Add fake features to integration crates 2020-01-21 08:17:49 -08:00
juniper_rocket Only run async tests on master for crates that require master 2020-01-21 09:22:14 -08:00
juniper_rocket_async Only run async tests on master for crates that require master 2020-01-21 09:22:14 -08:00
juniper_warp Release juniper_warp 0.5.2 2020-01-18 17:14:35 -08:00
.gitignore 0.9.2 release 2018-01-13 10:34:30 +01:00
.travis.yml (ci) Fix CI builds 2019-06-25 17:40:37 +02:00
azure-pipelines.yml (ci) Fix release automation check by pinning cargo-release to older version 2019-07-24 02:37:55 +02:00
Cargo.toml Turn off juniper_warp until it is fixed 2020-01-21 09:04:27 -08:00
CONTRIBUTING.md Improve contribution guide 2019-05-18 14:20:44 +02:00
LICENSE Initial import 2016-09-11 18:41:29 +02:00
Makefile.toml Add tests with async features enabled to CI 2020-01-20 23:05:08 -08:00
README.md Mention juniper-from-schema in README (#395) 2019-07-19 13:19:42 -07:00
RELEASING.md Update RELEASING.md 2019-05-16 19:22:20 -07:00
rustfmt.toml address clippy::all lints (#486) 2019-12-17 20:37:46 -08:00

Juniper

GraphQL server library for Rust

Build Status Build Status codecov Crates.io Gitter chat


GraphQL is a data query language developed by Facebook intended to serve mobile and web application frontends.

Juniper makes it possible to write GraphQL servers in Rust that are type-safe and blazingly fast. We also try to make declaring and resolving GraphQL schemas as convenient as possible as Rust will allow.

Juniper does not include a web server - instead it provides building blocks to make integration with existing servers straightforward. It optionally provides a pre-built integration for the Hyper, Iron, Rocket, and Warp frameworks, including embedded Graphiql and GraphQL Playground for easy debugging.

The book is also available for the master branch and older versions published after 0.11.1. See the book index.

Getting Started

The best place to get started is the Juniper Book, which contains guides with plenty of examples, covering all features of Juniper. (very much WIP)

To get started quickly and get a feel for Juniper, check out the Quickstart section.

For specific information about macros, types and the Juniper api, the API Reference is the best place to look.

You can also check out src/tests/schema.rs to see a complex schema including polymorphism with traits and interfaces. For an example of web framework integration, see the hyper, rocket, iron, and warp examples folders.

Features

Juniper supports the full GraphQL query language according to the specification, including interfaces, unions, schema introspection, and validations. It does not, however, support the schema language. Consider using juniper-from-schema for generating code from a schema file.

As an exception to other GraphQL libraries for other languages, Juniper builds non-null types by default. A field of type Vec<Episode> will be converted into [Episode!]!. The corresponding Rust type for e.g. [Episode] would be Option<Vec<Option<Episode>>>.

Integrations

Data types

Juniper has automatic integration with some very common Rust crates to make building schemas a breeze. The types from these crates will be usable in your Schemas automatically.

Web Frameworks

Guides & Examples

API Stability

Juniper has not reached 1.0 yet, thus some API instability should be expected.