Following the implementation of graphql-constraint-directive, we encountered a failing test.
This test aimed to ensure that mutations would fail under specific conditions.
Instead of correctly handling the mutation failure with this message : Schema is not configured to execute mutation operation.
It would throw the following error :
Hello!
Following the implementation of graphql-constraint-directive, we encountered a failing test. This test aimed to ensure that mutations would fail under specific conditions.
Instead of correctly handling the mutation failure with this message :
Schema is not configured to execute mutation operation.
It would throw the following error :{ "errors": [ { "message": "Cannot read properties of undefined (reading 'getFields')" } ] }
These changes address this issue, ensuring that mutations fail gracefully. We also added a test to validate this behavior.