This version 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.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Your app is only affected if you use hoodie as a hapi plugin within your existing hapi app. Instead of passing options.db that would get passed to a PouchDB constructor internally, you know pass in options.PouchDB directly, with all defaults and adapters already set as your app requires it. With that the hapi usage of hoodie is coherent with @hoodie/server, @hoodie/account-server and @hoodie/store-server
With Integrationsfirst-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.
Screencast Try it today. Free for private repositories during beta.
Hello lovely humans,
hoodie just published its new version 27.0.0.
This version 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.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
GitHub Release
27.0.0 (2017-01-23)
Bug Fixes
GET /unknown(5429f284)Features
Breaking Changes
Before all data was stored with pouchdb-adapter-leveldb by default. With that version, pouchdb-adapter-fs is used instead.
To keep using the LevelDB adapter as default, set the
dbAdapteroption topouchdb-adapter-leveldband instal the adapter as dependency of your app.(0a312f05)
Your app is only affected if you use
hoodieas a hapi plugin within your existing hapi app. Instead of passingoptions.dbthat would get passed to a PouchDB constructor internally, you know pass inoptions.PouchDBdirectly, with all defaults and adapters already set as your app requires it. With that the hapi usage ofhoodieis coherent with@hoodie/server,@hoodie/account-serverand@hoodie/store-server(e110920f)
Screencast
Try it today. Free for private repositories during beta.