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

Conversation

@ghengeveld
Copy link
Member

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.

  • Enable experimental support for Suspense by passing the suspense flag [@ghengeveld in #153]
  • Allow overriding fetch's resource argument when invoking run through useFetch [@ghengeveld in #150]
  • Make sure useFetch rejects with an Error type [@artdent in #114]
  • Fix the promise render prop, so it's always a Promise [@ghengeveld in #148]
  • Add displayName to the createInstance TypeScript definition [@artdent in #102]
  • Fix TypeScript module interop by avoiding synthetic default imports [@rokoroku in #112]
  • Remove some TypeScript definitions without implementation [@Khartir in #107]
  • Setup new documentation site (https://docs.react-async.com)

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 Aug 23, 2019
* updated contribute to run examples

* updated examples md
…with isPending, since this is the preferred terminology.
ghengeveld added 24 commits Oct 6, 2019
@ghengeveld ghengeveld requested a review from phryneas Oct 7, 2019
@ghengeveld ghengeveld merged commit 8aa1417 into master Oct 7, 2019
14 of 16 checks passed
14 of 16 checks passed
codecov/patch 96% of diff hit (target 98.93%)
Details
codecov/project 98.72% (-0.21%) compared to add133c
Details
CodeFactor No issues found.
Details
DeepScan 0 new and 0 fixed issues
Details
Travis CI - Branch Build Passed
Details
Travis CI - Pull Request Build Passed
Details
ci/chromatic 1 story unchanged.
Details
ci/circleci: build Your tests passed on CircleCI!
Details
ci/circleci: chromatic Your tests passed on CircleCI!
Details
ci/circleci: coverage Your tests passed on CircleCI!
Details
ci/circleci: examples Your tests passed on CircleCI!
Details
ci/circleci: lint Your tests passed on CircleCI!
Details
ci/circleci: test Your tests passed on CircleCI!
Details
ci/codesandbox Building packages succeeded.
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details
continuous-integration/travis-ci/push The Travis CI build passed
Details
@ghengeveld ghengeveld deleted the release branch Oct 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
8 participants
You can’t perform that action at this time.