Update @hoodie/account-client to the latest version 🚀 #18
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.
Version 6.0.0 of @hoodie/account-client just got published.
The version 6.0.0 is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of @hoodie/account-client.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Release Notes
v6.0.0<a name"6.0.0">
6.0.0 (2017-03-09)
Features
account.get()
(188300a2)account.get()
(99d080ef)Breaking Changes
account.ready
has been removed. All APIs are now asynchronous, no setup is needed any longer(22d8c159)
*
account.fetch()
andaccount.profile.fetch()
have been removed. Useaccount.get()
andaccount.profile.get()
instead(e5c1af20)
*
account.profile.get()
returns a promise now. It also sends a requestto the server requesting the current user’s profile properties unless
options.local
is set to true(188300a2)
*
account.get()
returns a promise now. It also sends a request to the server requested the current user’s account properties unless one of the following conditions is trueid
and orsession
properties are requestedoptions.local
is set to true(99d080ef)
*
account.hasInvalidSession()
has been removed. Useaccount.get(session.invalid)
instead.(0a998f7d)
*
account.isSignedIn()
has been removed. Useaccount.get(session)
instead.(c2a87220)
Commits
The new version differs by 27 commits .
22d8c15
breaking: remove
account.ready
1c7c6b4
test: remove
account.ready
0e48cba
docs(README): remove
account.ready
e5c1af2
breaking: remove
account.fetch()
andaccount.profile.fetch()
616e227
test: remove
account.fetch()
eeefd83
docs(README): remove
account.fetch()
andaccount.profile.fetch()
188300a
feat: async
account.get()
a75c728
test: async
account.profile.get()
715ed3e
docs(README): async
account.profile.get()
6c2be7f
docs(README): async
account.get()
99d080e
feat: async
account.get()
3e91525
test: async
account.get()
0a998f7
breaking: remove
account.hasInvalidSession()
6a811dd
test: remove
account.hasInvalidSession()
API59515bd
docs(README): remove
account.hasInvalidSession()
There are 27 commits in total. See the full diff.
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴