-
Notifications
You must be signed in to change notification settings - Fork 8.4k
[#18077] [expo-sqlite] Support nulls in query args #18078
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.
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
[#18077] [expo-sqlite] Support nulls in query args #18078
Conversation
…ng in the test suite!)
…dy passing in the test suite!)" This reverts commit 85ad615.
The test suite errors look to my eyes like red herrings. But caveat: I haven't contributed to this repo before. But on all three platforms the failure is the same: the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello @tsheaff 👋
Thank you for this contribution 😁
It looks good, so I'll merge it right away 🚀
Don't worry about the CI being red - we're having some problems with it lately 😅
Thanks @bbarthec ! How often do you reelase new version of |
@tsheaff, I believe |
# Why #18078 fixed this for the callback-based functions, but not for `executeSqlAsync`. Changing the parameters for the `args` of that function to match.
# Why expo#18078 fixed this for the callback-based functions, but not for `executeSqlAsync`. Changing the parameters for the `args` of that function to match.
Why
Please see #18077 for full motivation
How
Update the types of
executeSql > args
param from(number | string)[]
to(number | string | null)[]
Test Plan
There is already a test passing for this behavior in the test suite! See here. This test is in JS not TS, so no issue was raised on the type mismatch.
Checklist
expo build
(eg: updated@expo/xdl
).expo prebuild
& EAS Build (eg: updated a module plugin).