You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, I think that in this instance Lighthouse is right in returning a 200 anyways. It would be reasonable to send more then one operations and have one of them fail validation and the other pass completely, which according to the spec MUST result in a 200. Also, they might fail due to unrelated reasons, e.g. authorization. Which would be the correct status code then?
Only failures that completely prevent the execution of any operations at all should be non-200.
Describe the bug
I have a Mutation register and when I will have a unique error for the email field I want a 422 status code for it but it always returns 200
I have already seen #279
Expected behavior/Solution
It should return 422
Output/Logs
Lighthouse Version
5.0
The text was updated successfully, but these errors were encountered: