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
Typegen doesn't accept absolute path for generates.
To Reproduce
Steps to reproduce the behavior:
Create a sanity-typegen.json with an absolute path in generates
Extract schema: sanity schema extract
Run Typegen: sanity typegen generate
Typegen returns success, saying it has created a file at the given path, however it doesn't exist.
The path is interpreted as relative and created in the sanity directory, not the one actually defined.
Expected behavior
Types are written to the configured file.
Which versions of Sanity are you using?
3.60.0
@sanity/cli (global) 3.60.0 (up to date)
@sanity/asset-utils 2.0.6 (up to date)
@sanity/eslint-config-studio 4.0.0 (up to date)
@sanity/icons 3.4.0 (up to date)
@sanity/language-filter 4.0.2 (up to date)
@sanity/locale-de-de 1.1.11 (up to date)
@sanity/orderable-document-list 1.2.2 (up to date)
@sanity/ui 2.8.9 (up to date)
@sanity/util 3.60.0 (up to date)
@sanity/vision 3.60.0 (up to date)
sanity 3.60.0 (up to date)
What operating system are you using?
Linux Mint 21.3 Virginia, Kernel 5.15.0-118
Which versions of Node.js / npm are you running?
node 20.18.0
pnpm 9.12.1
(npm 10.9.0 installed)
The text was updated successfully, but these errors were encountered:
Describe the bug
Typegen doesn't accept absolute path for
generates
.To Reproduce
Steps to reproduce the behavior:
generates
sanity schema extract
sanity typegen generate
Typegen returns success, saying it has created a file at the given path, however it doesn't exist.
The path is interpreted as relative and created in the sanity directory, not the one actually defined.
Expected behavior
Types are written to the configured file.
Which versions of Sanity are you using?
3.60.0
What operating system are you using?
Linux Mint 21.3 Virginia, Kernel 5.15.0-118
Which versions of Node.js / npm are you running?
node 20.18.0
pnpm 9.12.1
(npm 10.9.0 installed)
The text was updated successfully, but these errors were encountered: