Vlastimil Eliáš

Results 29 comments of Vlastimil Eliáš

OK, looks like solution for tests is to wrap whole `describe` part into function, and then call it twice from two other `describe` parts for each type of server side...

@confuser friendly reminder :-D I'd like to agree how to proceed next.

@confuser testsuite updated to reuse tests for both implementations, best example is `/test/argument.test.js`. Only part of tests covering implemented features is running for the new server validator implementation for now....

@confuser looks like server plugin implementation is finished, any comments welcome

I believe it is ready to review 😀

Sorry, I noticed improvement in Envelop plugin and README, now it is really done :-)

@confuser any progress ;-)

This approach allows to keep Schema as is, without changing types to custom scalars. So in schema there will be common String or Int, but query validation will be applied...

And this might also solve Apollo Federation issue #41 as federation runs in Apollo Server so I believe `validationRules` can be used there (not tested from me).

Good point, but looks like there is a workaround, by providing variables during the rule construction. For example see how [graphql-query-complexity plugin](https://github.com/slicknode/graphql-query-complexity#usage-with-express-graphql) solves it. But this probably limits usage of...