hoodiehq / hoodie-task-client Goto Github PK

Version 1.2.3 of memdown just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As memdown is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

the current TaskQueue constructor only accepts an id, the URL is hardcoded. Which makes it much less flexible. I think it would be a good idea to match the API of the Store constructor here: https://github.com/hoodiehq/pouchdb-hoodie-store#api

We should enforce options.remote or remoteBaseUrl being set, as tasks don't make sense without a backend counterpart

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Added the new Node.js version to your .travis.yml

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

Your Greenkeeper Bot 🌴

current status:

npm run test:coverage

...
=============================== Coverage summary ===============================
Statements   : 73.33% ( 33/45 )
Branches     : 47.62% ( 10/21 )
Functions    : 85.71% ( 6/7 )
Lines        : 74.42% ( 32/43 )
================================================================================

• claim this issue (@ddmck)
• start a pull request
• write tests until 100% coverage is reached
• review & merge

Ping us in the Hoodie Chat or on Twitter if you have ​​_any_​​ questions

Version 1.2.6 of memdown just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As memdown is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

This issue is reserved for participants of Welcome to Open Source, Atlanta.
If it’s still available after April 2nd, it’s all yours :)

🐛 The Bug

In the testing section of this repository’s README we tell the user to clone the repository using git clone [email protected]:hoodiehq/hoodie-client-task.git. But GitHub itself recommends the https:// protocol instead of the git@ which is SSH (see which remote should I use).

🎯 The Goal

Replace the git clone [email protected]:hoodiehq/hoodie-client-task.git with https://github.com/hoodiehq/hoodie-client-task.git in the README

📋 Step by Step

If this is your first, welcome 🎉 😄 Here is a great tutorial on how to send a pull request

• claim this issue (comment below)
• Clone the repository to your computer
• Edit the README.md file.
• Commit the change docs(README): fixed git clone URL
• Start a Pull Request. Mention closes #26 in the description of the pull request
• Done 👍 Comment below to ask for a review :)

Ping us in the Hoodie Chat or on Twitter if you have any questions :)

follow up for hoodiehq/hoodie#145

e.g.

hoodie.task.start('message', {
  to: '[email protected]',
  message: 'wazzzup?'
}, {
  timeout: 10000
}).catch( function( error ) {
  // { error: 'timeout' } 
});

Version 14.2.0 of browserify just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As browserify is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

follow up for #36.

We should add integration tests for the 3 main cases:

1. Create a task which succeeds
2. Create a task which errors
3. Create a task which gets a progress update

I would suggest we mock out @hoodie/store-client using proxyquire for the tests. We can simulate any events we want for the respective cases and can check if the right methods have been called.

To support development directly against this repo, a version must be added to the package to avoid npm install failures.