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.

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

Release v9.0.0 #151

Merged
merged 122 commits into from
Oct 7, 2019
Merged

Release v9.0.0 #151

merged 122 commits into from
Oct 7, 2019

Conversation

ghengeveld
Copy link
Member

@ghengeveld ghengeveld commented Sep 28, 2019

v9.0.0: The one with Suspense support

This release adds basic, experimental support for Suspense. Furthermore it contains mostly bugfixes, one of which causes a minor but breaking change for useFetch.

Breaking changes

useFetch rejection type

Previously with useFetch, a failure response would reject with the response object. It's better for rejections to be of type Error so that the full stack trace information is available. Also, the TypeScript type definition assumes that the error object is always an instance of Error. Therefore, the rejection value is now of type FetchError (a subclass of Error) which adds the response property so you can still access the underlying response, without breaking contract.

What to do:

  • If you are using useFetch and are using the error value, expecting it to be of type Response, you must now use error.response instead.

Experimental Suspense support

Due to its experimental nature, we may make breaking changes to this feature even in minor or patch releases, until Suspense for data fetching is officially released. Until then, this is marked experimental.

ghengeveld and others added 30 commits August 23, 2019 23:25
* updated contribute to run examples

* updated examples md
…with isPending, since this is the preferred terminology.
@ghengeveld ghengeveld requested a review from phryneas October 7, 2019 08:32
@ghengeveld ghengeveld merged commit 8aa1417 into master Oct 7, 2019
@ghengeveld ghengeveld deleted the release branch October 7, 2019 09:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants