Conversation
a61d843 to
cbc3286
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to master, this PR will be updated.
Releases
apollo-angular@14.0.0
Major Changes
#2395
4e9f107Thanks @JesseZomer! - BREAKING CHANGE: HTTP errors now return
Apollo Client's
ServerErrorinstead of Angular'sHttpErrorResponseWhen Apollo Server returns non-2xx HTTP status codes (status >= 300), apollo-angular's HTTP links
now return
ServerErrorfrom@apollo/client/errorsinstead of Angular'sHttpErrorResponse.This enables proper error detection in errorLinks using
ServerError.is(error)and providesconsistent error handling with Apollo Client's ecosystem.
Migration Guide:
Before:
After:
Properties Changed:
err.status→err.statusCodeerr.error→err.bodyText(always string, JSON stringified for objects)err.headers(Angular HttpHeaders) →err.response.headers(native Headers)err.responsewhich includes:status,statusText,ok,url,type,redirectedNote: This only affects HTTP-level errors (status >= 300). Network errors and other error
types remain unchanged. GraphQL errors in the response body are still processed normally through
Apollo Client's error handling.
Fixes HttpErrorResponse error in ErrorLink #2394
Patch Changes
8d2be64Thanks @vz-tl! - Allow headers type in DefaultContext to be Record or
HttpHeaders