From 99c1d9af689e5325f3cf535c4007b3aeb8325229 Mon Sep 17 00:00:00 2001
From: Minteck <contact@minteck.org>
Date: Tue, 10 Jan 2023 14:54:04 +0100
Subject: Update - This is an automated commit

---
 .../validation/rules/OverlappingFieldsCanBeMergedRule.d.ts  | 13 -------------
 1 file changed, 13 deletions(-)
 delete 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
deleted file mode 100644
index c1671c2..0000000
--- a/alarm/node_modules/graphql/validation/rules/OverlappingFieldsCanBeMergedRule.d.ts
+++ /dev/null
@@ -1,13 +0,0 @@
-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