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
Hey, while using the next version of xata client I found out that after doing a select query, get first etc. returned data is typed in the way that id is available. But whenever I log the data or try to access id, it is not available.
To Reproduce
Just make a normal read query and check the result and type with next version of xata client.
Expected behavior
Either id is defined in result, or id is removed from the type. I personally think that leaving id field is good idea, as using xata_id or doing it manually seems like an issue for me.
Describe the bug
Hey, while using the next version of xata client I found out that after doing a select query, get first etc. returned data is typed in the way that
id
is available. But whenever I log the data or try to accessid
, it is not available.To Reproduce
Just make a normal read query and check the result and type with next version of xata client.
Expected behavior
Either
id
is defined in result, orid
is removed from the type. I personally think that leavingid
field is good idea, as usingxata_id
or doing it manually seems like an issue for me.Software version
"@xata.io/client": "0.0.0-next.v0b9131efdfa1340c28d4ce9bd73d6c4854e7c140",
Additional context
Nope
The text was updated successfully, but these errors were encountered: