hoodiehq / hoodie-store-client

100%

master: 100%

LAST BUILD ON BRANCH 114-update-find-then-update

branch: 114-update-find-then-update

CHANGE BRANCH

x

Reset

• 114-update-find-then-update
• master
• run-coverage-on-all-prs
• 123/test-coverage
• greenkeeper-pouchdb-hoodie-api-1.6.3
• greenkeeper-pouchdb-hoodie-api-1.6.4
• greenkeeper-pouchdb-6.0.4
• greenkeeper-memdown-1.2.1
• greenkeeper-memdown-1.2.2
• greenkeeper-pouchdb-6.0.5
• greenkeeper-standard-8.1.0
• greenkeeper-lodash-4.16.0
• typeError-for-store-without-type
• greenkeeper-lodash-4.16.1
• scoped-score-type-conflict
• greenkeeper-zuul-3.11.1
• greenkeeper-lodash-4.16.2
• greenkeeper-standard-8.2.0
• greenkeeper-standard-8.3.0
• greenkeeper-tape-4.6.1
• greenkeeper-pouchdb-6.0.6
• greenkeeper-tape-4.6.2
• incorrect-events-in-scoped-stores
• greenkeeper-lodash-4.16.3
• greenkeeper-lodash-4.16.4
• greenkeeper-standard-8.4.0
• greenkeeper-pouchdb-6.0.7
• greenkeeper-browserify-13.1.1
• hoodie/612/scoped-store-reset-bug
• 134/pouchdb-option
• 138/is-persistent-using-pouchdb
• 138/remove-has-local-changes
• hoodie/652/constructor-bug
• pmbanugo-patch-1
• next
• 145/async-remote
• first-timers-only-update-license
• hoodiehq/camp#121
• add-update-events-from-remote
• 157/options-remote-getter
• code-coverage
• fix-non-semver-pouchdb-package-versions
• correctly-cleanup-reset-listener
• dev_mbad0la_options_validate
• dev-mbadola-validate-update

Build # 512

Build Type

push

travis-ci

Committed by gr2m

Commit Message

fix: store('scope').update() ignores scope

Ensures that when calling `store('scope').update(...)`, that only items in scope are updated.  Items out of scope are ignored.

This code assumes the following:
* `storedObjects` is an array with the exact same size as `objectsOrIds`
* `objectsOrIds` is either a string, an object, a list of strings, or a list of objects
* if `objectsOrIds` is not an array then it is a single string representing an id or a single object and, as a result, `storedObjects` will either be null or a single object
* when attempting to find a single objectOrId, a single object is returned (rather than an array with one object)
* every item returned by find() will have an id associated with it.

Run Details

307 of 307 relevant lines covered (100.0%)

29.65 hits per line