-
Notifications
You must be signed in to change notification settings - Fork 9
Update hoodie to the latest version 🚀 #21
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
base: master
Are you sure you want to change the base?
Conversation
Version 28.1.0 just got published.Update to this version instead 🚀 Release Notesv28.1.0<a name"28.1.0"> 28.1.0 (2017-03-15)Features
|
Version 28.1.1 just got published.Update to this version instead 🚀 Release Notesv28.1.1<a name"28.1.1"> 28.1.1 (2017-05-25)Bug Fixes
CommitsThe new version differs by 20 commits.
There are 20 commits in total. See the full diff |
Version 28.1.2 just got published.Update to this version instead 🚀 Release Notesv28.1.2<a name"28.1.2"> 28.1.2 (2017-06-03)Bug FixesCommitsThe new version differs by 5 commits.
See the full diff |
gr2m
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The hoodie client usage needs to be adapted before merging:
https://github.com/hoodiehq/hoodie-app-skeleton/blob/master/public/assets/js/login.js
Version 28.1.3 just got published.Update to this version instead 🚀 Release Notesv28.1.3<a name"28.1.3"> 28.1.3 (2017-06-04)Bug Fixes
|
Version 28.1.4 just got published.Update to this version instead 🚀 Release Notesv28.1.4<a name"28.1.4"> 28.1.4 (2017-06-08)Bug Fixes
CommitsThe new version differs by 8 commits.
See the full diff |
Version 28.1.5 just got published.Update to this version instead 🚀 Release Notesv28.1.5<a name"28.1.5"> 28.1.5 (2017-06-09)Bug Fixes
CommitsThe new version differs by 1 commits.
See the full diff |
Version 28.2.1 just got published.Update to this version instead 🚀 Release Notesv28.2.1<a name"28.2.1"> 28.2.1 (2017-07-02)Bug FixesCommitsThe new version differs by 5 commits.
See the full diff |
Version 28.2.2 just got published.Update to this version instead 🚀 Release Notesv28.2.2<a name"28.2.2"> 28.2.2 (2017-08-12)Bug Fixes
CommitsThe new version differs by 6 commits.
See the full diff |
Version 28.2.3 just got published.Update to this version instead 🚀 CommitsThe new version differs by 14 commits.
See the full diff |
Version 28.2.5 just got published.Update to this version instead 🚀 Release Notesv28.2.528.2.5 (2018-01-06)Bug Fixes
CommitsThe new version differs by 7 commits.
See the full diff |
Version 28.2.6 just got published.Update to this version instead 🚀 CommitsThe new version differs by 4 commits.
See the full diff |
Version 28.0.0 of hoodie just got published.
The version 28.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.
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
v28.0.0<a name"28.0.0">
28.0.0 (2017-03-09)
Breaking Changes
For
hoodie.store:Before, change events (incl. add, update, remove) have only been triggered when using the custom APIs like
.add()or.update(). Now they get always triggered, including for changes replicated into the database. hoodiehq/pouchdb-hoodie-api@1958c42the order of when the methods’ promises resolve and the events get triggered cannot be guaranteed as we rely on PouchDB’s .changes(). We would love to enforce promises to resolve after changes get emitted, but the required complexity to do that is not worth it.
separate methods like
require(pouchdb-hoodie-api/add)can no longer be required directlyThe reason for that is that all the methods now also accept a
prefixargument which by default is null. That way we don’t need to implement each method twice, once forstore.add, and once forstore.withIdPrefix(test/).addWe no longer map PouchDB’s
._idproperty to.id, instead we pass trough docs from PouchDB 1:1. Also the timestamps are now all namespaced with.hoodie(doc.createdAtbecomesdoc.hoodie.createdAt)For
hoodie.account:account.readyhas been removed. All APIs are now asynchronous, no setup is needed any longeraccount.fetch()andaccount.profile.fetch()have been removed. Useaccount.get()andacc*account.fetch()andaccount.profile.fetch()have been removed. Useaccount.get()andacc*account.fetch()andaccount.profile.fetch()have been removed. Useaccount.get()andacc*account.fetch()andaccount.profile.fetch()have been removedrequest *account.fetch()andaccount.profile.fetch()have been removed. Useaccount.following conditions is trueidand orsessionproperties are requestedoptions.localis set to trueaccount.hasInvalidSession()has been removed. Useaccount.get(session)instead (check ofsession.invalid)account.isSignedIn()has been removed. Useaccount.get(session)instead.(9d636fa8)
*
The store instance which
server.plugins.store.api.open(dbName)resolves tohas several breaking changes via [email protected]
Before, change events (incl. add, update, remove) have only been triggered
when using the custom APIs like
.add()or.update(). Now they get alwaystriggered, including for changes replicated into the database.
the order of when the methods’ promises resolve and the events get triggered
cannot be guaranteed as we rely on PouchDB’s
.changes(). We would love toenforce promises to resolve after changes get emitted, but the required
complexity to do that is not worth it.
We no longer map PouchDB’s ._id property to .id, instead we pass trough docs
from PouchDB 1:1. Also the timestamps are now all namespaced with
.hoodie(doc.createdAtbecomesdoc.hoodie.createdAt)Unless you use the
server.plugins.store.api.open(name)API you are not affected by any of this.(ba5301f2)
Commits
The new version differs by 10 commits .
d8d9c86chore: adapt to@hoodie/client@109d636fabreaking(package): @hoodie/client@10ba5301fbreaking(package): @hoodie/server@2359d67abdocs: correcting missing 'install' command0e3ebfedocs: update for docs chicken img & local buildaa2e25ddocs: adding docs chicken imagec54d790docs(contributing): Code highlighting (#715)f3bafacstyle: standard31e4a6echore(package): update standard to version 9.0.00ae9bc6docs: get readthedocs to build (#705)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 🌴