GraphQL server library for Rust
Find a file
Christian Legnitto f0ccc2e35e
Compile and test juniper_hyper on stable (#616)
This file was put in place to work around a bug. The fix has now
made it to stable.
2020-04-10 00:16:03 -10:00
.github Use github action to download cargo-make (#594) 2020-03-30 20:03:44 -07: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 Clippy cleanup (#579) 2020-03-20 09:11:06 -07:00
docs/book doc: remove outdated examples from third-party integrations list (#572) 2020-03-18 20:46:32 -07:00
examples Minor improvements to subscriptions functionality (#591) 2020-03-30 20:43:00 -07:00
integration_tests Added document validation in the resolve_into_stream method and a test (#604) 2020-04-05 11:59:10 -10:00
juniper Move graphiql export location (#615) 2020-04-10 00:06:39 -10:00
juniper_benchmarks Clippy cleanup (#579) 2020-03-20 09:11:06 -07:00
juniper_codegen Fix some clippy warnings (#595) 2020-03-31 08:34:50 -07:00
juniper_hyper Compile and test juniper_hyper on stable (#616) 2020-04-10 00:16:03 -10:00
juniper_iron Move graphiql export location (#615) 2020-04-10 00:06:39 -10:00
juniper_rocket Move graphiql export location (#615) 2020-04-10 00:06:39 -10:00
juniper_rocket_async Move graphiql export location (#615) 2020-04-10 00:06:39 -10:00
juniper_subscriptions Removed 'compat' feature from futures on juniper_subscriptions and juniper_warp (#606) 2020-04-08 15:40:22 -10:00
juniper_warp Move graphiql export location (#615) 2020-04-10 00:06:39 -10:00
.gitignore 0.9.2 release 2018-01-13 10:34:30 +01:00
azure-pipelines.yml Update images for azure pipelines (#555) 2020-03-09 00:12:11 -07:00
Cargo.toml Update rocket_async to central GraphQLBatch* enums (#612) 2020-04-09 22:10:24 -10: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 Remove async feature gate (#554) 2020-03-08 23:20:11 -07:00
README.md Update README.md (#535) 2020-02-20 23:22:40 -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 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 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.