You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just found that the 2D array field teamIdPairsis the culprit. Is there anything I can do to remove this type error without changing teamIdPairs?
Hello,
I ran into a typescript error with db.table.update() or db.table.bulkUpdate(). It complains that the changes values have issues:
TS2322: Type number is not assignable to type void | PropModification | undefined dexie.d.ts(388, 29): The expected type comes from property activated which is declared here on type
Thanks for the repro. The issue was that the mapped type KeyPaths<T> got into an eternal loop on 2D arrays because the test whether the inner type was an object evaluated true also when the inner type was a nested array and arrays can have an infinite number of keys so the type system had to give up and resolved KeyPaths<Playlist> as a string. KeyPathValue<string> evaluated to undefined/void though (but should probably evaluate to any).
Updated:
I just found that the 2D array field
teamIdPairs
is the culprit. Is there anything I can do to remove this type error without changing teamIdPairs?Hello,
I ran into a typescript error with
db.table.update()
ordb.table.bulkUpdate()
. It complains that thechanges
values have issues:TS2322: Type number is not assignable to type void | PropModification | undefined dexie.d.ts(388, 29): The expected type comes from property activated which is declared here on type
This is the main code:
Do you see any issues with the table interface
Playlist
?Example:
https://codesandbox.io/p/sandbox/dexie-issue-forked-djwxz6?file=%2Fsrc%2Findex.tsx
The text was updated successfully, but these errors were encountered: