Skip to content

Commit 46d5e09

Browse files
committed
chore(deps): update dependency graphql-inspector/core and add missing definitions
1 parent 382c1ea commit 46d5e09

File tree

11 files changed

+904
-85
lines changed

11 files changed

+904
-85
lines changed

integration-tests/tests/api/policy/policy-check.spec.ts

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -323,12 +323,13 @@ describe('Schema policy checks', () => {
323323
'',
324324
' - Deprecation reason is required for field foo in type Query. (source: policy-require-deprecation-reason)',
325325
'',
326-
'ℹ Detected 3 changes',
326+
'ℹ Detected 4 changes',
327327
'',
328328
' Safe changes:',
329329
' - Type User was added',
330330
' - Field user was added to object type Query',
331331
' - Field Query.foo is deprecated',
332+
' - Directive deprecated was added to field Query.foo',
332333
'',
333334
'View full report:',
334335
expect.any(String),

integration-tests/tests/api/schema/delete.spec.ts

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -210,7 +210,7 @@ test.concurrent(
210210
typeType: object type,
211211
},
212212
path: Query.bruv,
213-
reason: Removing a field is a breaking change. It is preferable to deprecate the field before removing it.,
213+
reason: Removing a field is a breaking change. It is preferable to deprecate the field before removing it. This applies to removed union fields as well, since removal breaks client operations that contain fragments that reference the removed type through direct (... on RemovedType) or indirect means such as __typename in the consumers.,
214214
type: FIELD_REMOVED,
215215
usageStatistics: null,
216216
}

0 commit comments

Comments
 (0)