enforcing pagination in relational resolvers

[shawnjones253]

Is there any way to enforce pagination or the usage of "take" with a maximum value?

For context, we're using the generated relational resolvers currently, but are hoping to implement graphql amount limiting / pagination across the API. Something similar to this.

In resolvers we've written ourselves, I'd simply replace the type of take in any args with something like createIntScalar from here.

I'm hoping (though it doesn't look possible) there is a way to do this without completely abandoning the auto-generated relational resolvers.

Thanks!

[shawnjones253]

@MichalLytek -- would you be open to a PR if I could find an elegant way to work this into the generator?

[mmmeff]

Bumping, curious if there's any blessed way to customize these relational resolvers at all a la middleware or something.

If we were to take a stab at a PR for this, what do you think is the best place to hook into @MichalLytek ?

I'm torn between pursuing a configuration option in typegraphql-prisma vs a middleware/decorator model in typegraphql proper.

[mmmeff]

For context, the relational resolvers in our case can expose tables with 100,000s of records. Without enforcing pagination, this is a very easy DOS vector for either intentional or accidental exploitation.

[MichalLytek]

If you want to make a PR, please make sure to hide this behind a generator option, like with the "Emit isAbstract decorator option".