Skip to content

fix: multiRemove should accept readonly string[] #787

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Mar 29, 2022
Merged

fix: multiRemove should accept readonly string[] #787

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
28817f4
fix: `multiRemove` should accept `readonly string[]`
tido64 Mar 28, 2022
254cf15
prettier
tido64 Mar 28, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion src/types.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -143,7 +143,10 @@ export type AsyncStorageStatic = {
*
* See https://react-native-async-storage.github.io/async-storage/docs/api#multiremove
*/
multiRemove: (keys: string[], callback?: MultiCallback) => Promise<void>;
multiRemove: (
keys: readonly string[],
callback?: MultiCallback
) => Promise<void>;

/**
* Batch operation to merge in existing and new values for a given set of
Expand Down