fix: return undefined
instead of null
for non existing keys
#260
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.
π Linked issue
Resolves #205
β Type of change
π Description
This is a rework of #206
By changes to this PR, storage returns
undefined
instead ofnull
when a key does not exist.On the downside, this change makes unstorage less consistent with local storage and Cloudflare KV when
getItem
returnsnull
when the key does not exist.On the benefits, more thinking this is less a breaking change for users but actually a fix since we were already listing
null
as a valid Storage value (which does exist!). And we reduce use of evil null. (sindresorhus/meta#7)π Checklist