Proposal: new validation directives about graphql

[danstarns]

@TreeMan360 Hey! We don't directly support this. Due to the way the library works - Given some Type Definitons we produce a CURD schema with autogenerated inputs. As the inputs are auto-generated any directive you apply on the initial type is not preserved. You can however extend upon our autogenerated inputs to get this to work, you need to play around with some tools and we can sure look at making this easier but here is the gist showing how to do it: https://gist.github.com/danstarns/e3956e1633ab9866bd0172dc85470659

[danstarns]

To enforce a maximum number of entities you probably want to use the existing limit argument;

query {
    movies {
        genres(limit: 2) {
            name
        }
    }
}

That being said - Validation directives are something we are looking into, and we are thinking of supporting a similar feature set to https://www.npmjs.com/package/graphql-constraint-directive.

[corysimmons]

For clarity, dropping a comment that I'd love Zod support in here somehow (should probably support every big validation lib tbh).

[Andy2003]

To enforce a maximum number of entities you probably want to use the existing limit argument;

this is not enforcing a maximum, since the user can query:

query {
    movies {
        genres(limit: 20000000) {
            name
        }
    }
}

But with the proposed directives implemented this query would will fail with an error.

Validation directives are something we are looking into, and we are thinking of supporting a similar feature set to https://www.npmjs.com/package/graphql-constraint-directive.

Sounds great!

[danstarns]

@Andy2003 Ah yes I see the value in the max limit here 👍

[TreeMan360]

I am trying to get https://www.npmjs.com/package/graphql-constraint-directive to work with this package. Is this possible?

[darrellwarde]

This is something we'll look at (at some point), and just pointing out a couple of proposed solutions from some other issues which I will be closing as duplicates of this:

• #1550
• #1383

[darrellwarde]

Given the amount of third party libraries already available for validations, we don't have the appetite to re-implement these behaviours in the library. However, we will aim to document how to use these libraries with our generated schema.