Fix typo in StorageArea.getKeys() documentation
#40661
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
Content:WebExt
rebloor
approved these changes
Aug 8, 2025
| @@ -49,7 +49,7 @@ Retrieve keys of all items in storage.local and log the result. | |||
| browser.storage.local | |||
| .getKeys() | |||
| .then((keys) => console.log(keys)) // [ "kitten", "monster" ] | |||
| .catch((err) => console.error(`Error: ${error}`)); | |||
| .catch((err) => console.error(`Error: ${err}`)); | |||
There was a problem hiding this comment.
Suggested change
| .catch((err) => console.error(`Error: ${err}`)); | |
| .catch((err) => console.error(`Error: ${err}`)); |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
The existing code sample uses the wrong variable name.
Motivation
I ran into this code sample when looking into https://bugzilla.mozilla.org/show_bug.cgi?id=1979997, where the error case is hit.
Additional details
N/A
Related issues and pull requests
Introduced in #40560.