getItem returns null for unknown key #58
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fixes #55
Changes
getItem
now returns null for unknown keyremoveItem
andpull
that were doingexpect(...).toBeUndefined()
Note
When given an array of keys like
['known1', 'unknown', 'known2']
, getItem returns[value1, undefined, value2]
. Maybe that 2nd value should be null for consistency?I left it as is since
getItem(array)
doesn't have an analog in localforage. Being different from localforage was the source of confusion in #55.