From 2c4ae43e688a9873e86211ea0e7aeb9ba770dd77 Mon Sep 17 00:00:00 2001
From: Minteck <contact@minteck.org>
Date: Tue, 18 Oct 2022 08:59:09 +0200
Subject: Update

---
 .../validation/rules/OverlappingFieldsCanBeMergedRule.d.ts  | 13 +++++++++++++
 1 file changed, 13 insertions(+)
 create mode 100644 alarm/node_modules/graphql/validation/rules/OverlappingFieldsCanBeMergedRule.d.ts

(limited to 'alarm/node_modules/graphql/validation/rules/OverlappingFieldsCanBeMergedRule.d.ts')

diff --git a/alarm/node_modules/graphql/validation/rules/OverlappingFieldsCanBeMergedRule.d.ts b/alarm/node_modules/graphql/validation/rules/OverlappingFieldsCanBeMergedRule.d.ts
new file mode 100644
index 0000000..c1671c2
--- /dev/null
+++ b/alarm/node_modules/graphql/validation/rules/OverlappingFieldsCanBeMergedRule.d.ts
@@ -0,0 +1,13 @@
+import { ASTVisitor } from '../../language/visitor';
+import { ValidationContext } from '../ValidationContext';
+
+/**
+ * Overlapping fields can be merged
+ *
+ * A selection set is only valid if all fields (including spreading any
+ * fragments) either correspond to distinct response names or can be merged
+ * without ambiguity.
+ */
+export function OverlappingFieldsCanBeMergedRule(
+  context: ValidationContext,
+): ASTVisitor;
-- 
cgit