Skip to content

fix: multiSet should expect read-only input #1103

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

Jump to bottom
Merged
merged 1 commit into from
Jun 17, 2024
Merged

fix: multiSet should expect read-only input #1103

merged 1 commit into from
Jun 17, 2024

Conversation

tido64
Copy link
Member

@tido64 tido64 commented Jun 14, 2024

Summary

Resolves #1101

Test Plan

n/a

@tido64 tido64 requested a review from krizzu as a code owner June 14, 2024 10:15
@tido64 tido64 merged commit 9993f6e into main Jun 17, 2024
@tido64 tido64 deleted the tido/multiset-readonly-input branch June 17, 2024 09:37
@krizzu krizzu mentioned this pull request Jul 11, 2024
Merged
r0h0gg6 pushed a commit to r0h0gg6/async-storage that referenced this pull request Jul 28, 2025
@tido64
fix: multiSet should expect read-only input (react-native-async-sto…
e87d564 
…rage#1103)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@krizzu krizzu krizzu approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

multiSet should expect a readonly input
2 participants
@tido64 @krizzu