This rule isn't actually part of the spec, and GraphQL-JS allows this construction.
From a compatibility standpoint, I don't think this poses any risks: any queries that were previously returned as invalid (wrongly) will now be executed. But I think anyone who encountered this in the past probably removed the !.
This rule isn't actually part of the spec, and GraphQL-JS allows this construction.
From a compatibility standpoint, I don't think this poses any risks: any queries that were previously returned as invalid (wrongly) will now be executed. But I think anyone who encountered this in the past probably removed the
!
.Fixes #5029