Open greenkeeper[bot] opened 7 years ago
Update to this version instead 🚀
.adapter
for .isPersistent()
(9b726bc7)Update to this version instead 🚀
Update to this version instead 🚀
<a name"8.0.0">
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
)
(852393e8)
Update to this version instead 🚀
<a name"8.0.1">
.withIdPrefix()
after .reset()
(3f0ccc4b)Update to this version instead 🚀
<a name"8.1.0">
options.remote
getter on setup (183af82a)The new version differs by 7 commits .
183af82
fix: don’t call options.remote
getter on setup
005118d
chore: remove undocumented store.reset behavior
bf82f2c
chore(package): add version placeholder
6b8fe92
test: options.remote
Promise
2b26cd2
feat(package): async options.remote via pouchdb-hoodie-sync@2.1.0
a6ac16d
docs(README): options.remote
Promise
dd8e47f
test: remove test for "change" event options.remote
See the full diff.
Update to this version instead 🚀
The new version differs by 23 commits.
670faa4
refactor: replace String.match with RegExp.test (#156)
d0bc7c8
docs: adapt comments to variable names
f526977
docs: event handlers don’t get an options argument
6cc3086
chore: remove unused cleare method
aacd8cf
docs(withIdPrefix): fix api comment
8f7e21d
test: fix assertion comment
a0f18eb
chore: remove unused util method
6b42cfb
refactor: use _.assign instead of _.merge
fa6ee76
chore(package): pouchdb-utils, pouchdb-errors
ba1e9c6
chore: remove use strict
24550de
fix: .withIdPrefix()
works after .reset()
f33c11e
chore(package): lie
95114ab
test: scoped store API works after reset
488b367
refactor: merge pouchdb-hoodie-sync
39171e6
test: merge `pouchdb-hoodie-sync
There are 23 commits in total.
See the full diff
Update to this version instead 🚀
<a name"8.1.3">
The new version differs by 7 commits.
4cd0b26
fix: add/update events based on doc existence in db
5f1c2ba
test: add/update events based on doc existence
7c7a47a
chore(package): fix versions for non-semver PouchDB packages
8d7ef4c
refactor: make addTimestamps mockable
98fd418
test: 100% test coverage
87df218
chore(package): semantic-release update
01cf067
chore(package): -greenkeeper-postpublish
See the full diff
Update to this version instead 🚀
<a name"8.1.4">
Update to this version instead 🚀
<a name"8.2.0">
Update to this version instead 🚀
<a name"8.3.0">
Version 6.0.0 of @hoodie/store-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/store-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.06.0.0 (2016-11-29)
Features
options.PouchDB
(removed as dependency) (e7d040bd)Breaking Changes
@hoodie/store-client
used to depend onpouchdb
. It has now been removed and replaced by the newPouchDB
option:BREAKING CHANGE:
options.ajax
has been removed. It was passed trough topouchdb-hoodie-sync
where it is used to dynamically set the
ajax
PouchDB option.For Hoodie, we used that to change the
Authorization
headerbased on user’s session. But instead of passing in an ajax
function to return the ajax setting dynamically, we will now
set a getter for
options.ajax.headers.authorization
that willreturn the right session ID dynamically. This will simplify the
implementation
(e7d040bd)
Commits
The new version differs by 6 commits .
190fd68
chore(package): pouchdb-hoodie-sync@^2.0.0
e7d040b
feat:
options.PouchDB
(removed as dependency)399edce
test: options.PouchDB
ebbe840
chore(package): remove pouchdb from dependencies
7dbb3aa
docs(README): PouchDB is now an option, no longer a dependency
fecd789
docs(README): new code coverage status URL
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: