search

hoodiehq / ember-hoodie

Build awesome offline-first Ember apps with Hoodie!
MIT License
17 stars 6 forks source link

Update @hoodie/client to the latest version 🚀 #43

Closed greenkeeper[bot] closed 7 years ago

greenkeeper[bot] commented 7 years ago

Version 9.0.1 of @hoodie/client just got published.

Dependency @hoodie/client
Current Version 8.0.3
Type dependency

The version 9.0.1 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/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 v9.0.1

9.0.1 (2017-01-10)

Bug Fixes

  • hoodie.ready race condition (67d2efb9)
Commits

The new version differs by 9 commits .

  • 67d2efb fix: hoodie.ready race condition
  • 71bb607 chore(package): update npm-run-all to version 4.0.0
  • 84d4c2a chore(package): update to latest @hoodie/{account-client,connection-status,store-client}
  • b131a74 chore(package): pouchdb-doc-api
  • 28b4966 feat: hoodie.ready
  • 1bd50a0 test: hoodie.ready
  • 1ff25b7 docs(README): hoodie.ready
  • d50bd4c refactor: use account.hook API
  • e3c80ed test: use account.hook API

See the full diff.

Not sure how things should work exactly? There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html) and of course you may always [ask my humans](https://github.com/greenkeeperio/greenkeeper/issues/new).

Your Greenkeeper Bot :palm_tree:

greenkeeper[bot] commented 7 years ago

Version 9.0.2 just got published.

Update to this version instead 🚀

Release Notes v9.0.2

9.0.2 (2017-01-14)

Bug Fixes

  • hoodie.ready to resolve with API, not return it, after setup finished (#122) (0a9ae93b)
Commits

The new version differs by 1 commits .

  • 0a9ae93 fix: hoodie.ready to resolve with API, not return it, after setup finished (#122)

See the full diff.

greenkeeper[bot] commented 7 years ago

Version 10.0.0 just got published.

Update to this version instead 🚀

Release Notes v10.0.0

<a name"10.0.0">

10.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@1958c42

  • 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 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 directly

    The reason for that is that all the methods now also accept a prefix argument which by default is null. That way we don’t need to implement each method twice, once for store.add, and once for store.withIdPrefix(test/).add

  • 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.createdAt becomes doc.hoodie.createdAt)

BREAKING CHANGE:

For hoodie.account:

  • account.ready has been removed. All APIs are now asynchronous, no setup is needed any longer

  • account.fetch() and account.profile.fetch() have been removed. Use account.get() and account.profile.get() instead

  • account.profile.get() returns a promise now. It also sends a request to the server requesting the current user’s profile properties unless options.local is set to true

  • 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 true

    1. User is signed out
    2. Only id and or session properties are requested
    3. options.local is set to true

  • account.hasInvalidSession() has been removed. Use account.get(session) instead (check of session.invalid)

  • account.isSignedIn() has been removed. Use account.get(session) instead.

(5ebdbb67)

Commits

The new version differs by 5 commits .

  • 50be93d chore: adapt for latest `@hoodie/{account,store}-client
  • d9e791b test: adapt for latest `@hoodie/{account,store}-client
  • 5ebdbb6 chore(package): @hoodie/account-client@6, @hoodie/store-client@8.1
  • f243535 docs(README): remove hoodie.ready
  • 07fe63f chore(package): update browserify to version 14.0.0

See the full diff.

greenkeeper[bot] commented 7 years ago

Version 10.0.1 just got published.

Update to this version instead 🚀

Release Notes v10.0.1

<a name"10.0.1">

10.0.1 (2017-03-17)

Bug Fixes

Commits

The new version differs by 1 commits .

  • c3be48c fix: start sync on reconnect event (#134)

See the full diff.

greenkeeper[bot] commented 7 years ago

Version 10.0.2 just got published.

Update to this version instead 🚀

Release Notes v10.0.2

<a name"10.0.2">

10.0.2 (2017-03-18)

Bug Fixes

  • doc: duplicate argument documentation (1e32931d)
Commits

The new version differs by 3 commits .

  • 1e32931 fix(doc): duplicate argument documentation
  • b852868 style: standard
  • 3d24b2a chore(package): update standard to version 9.0.2

See the full diff.