-
-
Notifications
You must be signed in to change notification settings - Fork 103
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
LegendState w Supabase is only getting one of my tasks from my tasks table #467
Comments
It's because you used a custom id field name (it defaults to "id"), so it's seeing every task as having an id of export const tasks$ = observable(
customSynced({
// ...,
fieldId: "task_id"
})
); We should probably be catching this with a warning. I'll leave this open as a note to do that. |
Awsome, that fixed the issue. Is this also affecting update and delete methods? when the primary key of the table is something other than 'id' I can list and create a new table entry with this syntax
however when i try to update with this
tasks on my client will be updated and deleted but there are no changes on my Supabase table. From the I've cleared async storage and that doesn't seem to be the issue. |
I've the same issue, |
I am attempting to try out LegendState with my Supabase database in React Native Expo. I already have many Tasks on my tasks table prior to integrating LegendState and have not created any using the LegendState interface. However, when I console log my tasks$.get(), it only shows one of my tasks from the table, and if I use the For component to try to render them all, only one task is shown. I've referenced both the LegendState docs and Supabase's blog for setup. Maybe I'm not understanding and this is the intended output?
This is my setup:
Here i try to see the contents:
The console.log response:
The text was updated successfully, but these errors were encountered: