From 190ba304c5bb158080e58256c17b89f9baffc353 Mon Sep 17 00:00:00 2001 From: Nicholas DeJaco <54116900+ndejaco2@users.noreply.github.com> Date: Fri, 13 Oct 2023 14:13:17 -0700 Subject: [PATCH] Update README.md --- hooks/AppSync_BreakingChangeDetection/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/hooks/AppSync_BreakingChangeDetection/README.md b/hooks/AppSync_BreakingChangeDetection/README.md index 5fd246bb..56476800 100644 --- a/hooks/AppSync_BreakingChangeDetection/README.md +++ b/hooks/AppSync_BreakingChangeDetection/README.md @@ -2,7 +2,7 @@ Validates that an AWS AppSync GraphQL schema update does not introduce a change that would break existing clients of the AWS AppSync GraphQL API. There are three categories of changes in a GraphQL schema: -- **Breaking**: These are changes that are not backwards incompatible for existing API clients, such as changing the return type of an existing field or removing a field from the schema. +- **Breaking**: These are changes that are backwards incompatible for existing API clients, such as changing the return type of an existing field or removing a field from the schema. - **Dangerous**: These are changes that may be dangerous for existing API clients but are not necessarily breaking, such as adding a new value in an Enum or changing the default value on an argument. - **Non-breaking**: These are changes that are backwards compatible for existing clients, such as adding a new field or type to the schema. @@ -174,4 +174,4 @@ Resources: SIMPLE, COMPLEX } -``` \ No newline at end of file +```