Proposal: add ability to filter via @auth directive about graphql

[danstarns]

I'm not too sure how Error could help with the ability to filter using the directive?

Mentioned is the correct behaviour for allow, your client needs to do the filtering, and it only restricts access.

I will say that we are working on an @auth(where), below, that will solve the issue raised in the title.

To Be Implemented

Enable the usage of a where key on an auth rule.

Given the current user.id is "123"

type User {
    id: ID
    name: String
}

extend type User @auth(rules: [{ operations: "*", where: { id: "$jwt.id" } }])

Then when a client issues a GraphQL query for users;

query {
    users {
        id
        name
    }
}

Behind the scenes the user's id will be conceptually prepended to the query;

query {
    users(where: { id: "123" }) {
        id
        name
    }
}

[Andy2003]

Behind the scenes the user's id will be conceptually prepended to the query;

This is exactly what I was requesting!

[darrellwarde]

This is now a feature of the library as of version 1.0.0-alpha.6.