Umbral GraphQL

A REST endpoint returns the shape you designed. A GraphQL endpoint returns the shape the caller designed — which is the whole appeal, and the reason this plugin makes you say yes on purpose. Point it at the models you already declared and it derives the schema: queries, relation traversal, mutations, and live subscriptions, with no resolver code to write and nothing to keep in sync by hand.

Install

cargo add umbral-graphql

Wire it up

use umbral::prelude::*;
use umbral_graphql::GraphqlPlugin;

let app = App::builder()
    .database("default", pool)
    .plugin(
        GraphqlPlugin::new()
            .expose("post")
            .expose("auth_user")
            .hide("auth_user", "email")   // exposing a model exposes EVERY column
            .mutable("post"),             // createPost / updatePost / deletePost
    )
    .build()?;

{ post(id: "1") { title author { username } comments { body } } }

Target: nothing leaves the database by accident

Exposing a model exposes every column on it, so reads and writes are separate opt-ins: expose makes a model readable, mutable makes it writable, subscribable makes it live. A read you got wrong leaks data; a write you got wrong destroys it.

A #[umbral(private)] column stays invisible until allow_private_if unlocks it for a caller who has earned it — and the schema stays one honest document, with the field always present and always nullable, because a caller without the unlock has to legally receive nothing.

What you get

• Schema derived from the model registry — queries, filters, and relations
• Mutations and live subscriptions, each a separate opt-in
• Relation fields batched through a per-request DataLoader, so no N+1
• #[umbral(private)] columns unlockable per caller, with one honest schema
• Unauthorized writes refused by name, not silently dropped
• GraphiQL explorer in dev