Open r0skar opened 5 months ago
@r0skar can you still reproduce this with the latest version of sanity
?
@sgulseth Not the OP but I'm still experiencing this on the latest version (3.57.0).
Still happening as of Sanity 3.62.3
Thanks for the update, and sorry the delay here. I think this is because of a conflicting type name when we serialize the type names to be compatible as a TS identifier.
Describe the bug
Using sanity-typegen to create GROQ query types results in wrong types.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
VideoBlockQResult["video"]["asset"]
should be of typePartial<MuxVideoAsset> | undefined
Which versions of Sanity are you using?
Run
sanity versions
in the terminal and copy-paste the result here.What operating system are you using?
Which versions of Node.js / npm are you running?