Confirmed users
764
edits
Labs/Jetpack/JEP/11: Difference between revisions
Jump to navigation
Jump to search
m
no edit summary
(→Testing the Existence of Multiple Items: has(keyArray) doesn't pass keyArray to callback) |
mNo edit summary |
||
| Line 247: | Line 247: | ||
* <code>onResult(key, value)</code> | * <code>onResult(key, value)</code> | ||
** <code>onResult(key, value)</code> is called for each key given in <code>keyArray</code>. | ** <code>onResult(key, value)</code> is called for each key given in <code>keyArray</code>. | ||
** If a given key does not exist in the store, <code>value</code> will be <code>undefined</code>. | |||
** Items are enumerated in the same order that their keys are given in <code>keyArray</code>. | |||
* <code>onResult(null, null)</code> | * <code>onResult(null, null)</code> | ||
** When all items are exhausted, <code>onResult(null, null)</code> is called to signal that enumeration is complete. | ** When all items are exhausted, <code>onResult(null, null)</code> is called to signal that enumeration is complete. | ||
| Line 267: | Line 269: | ||
* <code>onResult(key, value)</code> | * <code>onResult(key, value)</code> | ||
** <code>onResult(key, value)</code> is called for each key-value pair in the store. | ** <code>onResult(key, value)</code> is called for each key-value pair in the store. | ||
**The order of enumeration is arbitrary. | |||
* <code>onResult(null, null)</code> | * <code>onResult(null, null)</code> | ||
** When all items are exhausted, <code>onResult(null, null)</code> is called to signal that enumeration is complete. | ** When all items are exhausted, <code>onResult(null, null)</code> is called to signal that enumeration is complete. | ||
| Line 287: | Line 290: | ||
* <code>onResult(key)</code> | * <code>onResult(key)</code> | ||
** <code>onResult(key)</code> is called for each key in the store. | ** <code>onResult(key)</code> is called for each key in the store. | ||
** The order of enumeration is arbitrary. | |||
* <code>onResult(null)</code> | * <code>onResult(null)</code> | ||
** When all keys are exhausted, <code>onResult(null)</code> is called to signal that enumeration is complete. | ** When all keys are exhausted, <code>onResult(null)</code> is called to signal that enumeration is complete. | ||
| Line 309: | Line 313: | ||
* <code>onResult(value)</code> | * <code>onResult(value)</code> | ||
** <code>onResult(value)</code> is called for each key given in <code>keyArray</code>. | ** <code>onResult(value)</code> is called for each key given in <code>keyArray</code>. | ||
** If a given key does not exist in the store, <code>value</code> will be <code>undefined</code>. | |||
** Values are enumerated in the same order that their keys are given in <code>keyArray</code>. | |||
* <code>onResult(null)</code> | * <code>onResult(null)</code> | ||
** When all values are exhausted, <code>onResult(null)</code> is called to signal that enumeration is complete. | ** When all values are exhausted, <code>onResult(null)</code> is called to signal that enumeration is complete. | ||
** Because <code>value</code> will be undefined when a given key does not exist, <code>onResult</code> should always use strict equality (<code>===</code> instead of <code>==</code> or <code>!value</code>) when checking for the <code>null</code> signal so that an <code>undefined</code> value is not mistaken for it. | |||
* <code>onError(errorMessage, keyArray)</code> | * <code>onError(errorMessage, keyArray)</code> | ||
| Line 329: | Line 336: | ||
* <code>onResult(value)</code> | * <code>onResult(value)</code> | ||
** <code>onResult(value)</code> is called for each value in the store. | ** <code>onResult(value)</code> is called for each value in the store. | ||
** The order of enumeration is arbitrary. | |||
* <code>onResult(null)</code> | * <code>onResult(null)</code> | ||
** When all values are exhausted, <code>onResult(null)</code> is called to signal that enumeration is complete. | ** When all values are exhausted, <code>onResult(null)</code> is called to signal that enumeration is complete. | ||