Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update README.md for AppSync Breaking Change Hook #245

Merged
merged 1 commit into from
Oct 13, 2023
Merged

Update README.md for AppSync Breaking Change Hook #245

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions hooks/AppSync_BreakingChangeDetection/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down Expand Up @@ -174,4 +174,4 @@ Resources:
SIMPLE,
COMPLEX
}
```
```
Loading