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 Notesv6.0.0
6.0.0 (2016-11-29)
Features
options.PouchDB (removed as dependency) (e7d040bd)
Breaking Changes
@hoodie/store-client used to depend on pouchdb. It has now been
removed and replaced by the new PouchDB option:
var PouchDB =require('pouchdb-core')
.plugin(require('pouchdb-replication'))
.plugin(require('pouchdb-adapter-memory'))
.plugin(require('pouchdb-adapter-http'))
var Store =require('@hoodie/store-client')
var db =newStore('db', {
PouchDB: PouchDB,
remote:'http://localhost:5984/db-remote'
})
BREAKING CHANGE:
options.ajax has been removed. It was passed trough to pouchdb-hoodie-sync
where it is used to dynamically set the ajax PouchDB option.
For Hoodie, we used that to change the Authorization header
based 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 will
return the right session ID dynamically. This will simplify the
implementation
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).
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: