From 6fe9eb72e42fb4ae36435324148e8f96e871a26c Mon Sep 17 00:00:00 2001 From: Eugen Wissner Date: Fri, 18 Jun 2021 06:51:14 +0200 Subject: Fix merging fields with arguments executeField shouldn't assume that a selection has only one field with a given name, but it should take the first field. The underlying cause is a wrong pattern, which (because of the laziness) is executed only if the field has arguments. --- CHANGELOG.md | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'CHANGELOG.md') diff --git a/CHANGELOG.md b/CHANGELOG.md index 174e6dc..6abc211 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -23,6 +23,10 @@ and this project adheres to - `valuesOfCorrectTypeRule` doesn't check objects recursively since the validation traverser calls it on all object properties. - Validation of non-nullable values inside lists. +- `executeField` shouldn't assume that a selection has only one field with a + given name, but it should take the first field. The underlying cause is a + wrong pattern, which (because of the laziness) is executed only if the field + has arguments. ### Changed - `AST.Document.Value.List` and `AST.Document.ConstValue.ConstList` contain -- cgit v1.2.3