How did it even work and pass the tests?

[FluorescentHallucinogen]

If argument passes the constraint validation, errors is an empty array.

[FluorescentHallucinogen]

@vsimko Could you please publish a new v3.2.1 to NPM?

[FluorescentHallucinogen]

@vsimko Any plans to refine the tests to prevent something like that? 😉

[vsimko]

v3.2.1 published to npm
I'll come back to this later when I'll be again working on the graphql backend in my app.

Anyway, thanks for contributing.
Feel free to add more tests. 😉

[FluorescentHallucinogen]

@vsimko

Feel free to add more tests. 😉

Ok, I'll add more tests. Looks like it's not too hard. 😉

Could you please better implement #6? 🙏

I really need this feature for my project, but, unfortunately, I don’t have much experience in writing directives (at the moment, I’m only actively exploring everything related to GraphQL directives). You would help me a lot.

I've tried https://github.com/confuser/graphql-constraint-directive, but it has serious problems that make it almost unusable.

[ecker00]

I'm in the same boat as @FluorescentHallucinogen , seems that this library works better than graphql-constraint-directive, but would be awesome to have it working on both ARGUMENT_DEFINITION | INPUT_FIELD_DEFINITION. 👍