@sanity/sdk-react 3.8.0 → 3.9.0-next.20261006164105

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@sanity/sdk-react",
-  "version": "3.8.0",
+  "version": "3.9.0-next.20261006164105",
   "private": false,
   "description": "Sanity SDK React toolkit for Content OS",
   "keywords": [
@@ -45,7 +45,7 @@
     "@module-federation/runtime": "^2.9.2",
     "@sanity/client": "^8.9.0",
     "@sanity/message-protocol": "^0.24.0",
-    "@sanity/sdk": "3.8.0",
+    "@sanity/sdk": "3.9.0-next.20261006164105",
     "@sanity/types": "^6.17.0",
     "react-compiler-runtime": "^1.0.0",
     "react-error-boundary": "^6.1.6",
@@ -72,7 +72,7 @@
     "groq": "^6.15.0",
     "groq-js": "^2.0.0",
     "jsdom": "^30.1.2",
-    "oxfmt": "^0.71.0",
+    "oxfmt": "^0.72.0",
     "react": "^19.3.0",
     "react-dom": "^19.3.0",
     "rolldown": "^1.2.12",

package/src/hooks/document/useDocument.test-d.ts

@@ -0,0 +1,65 @@
+import {createDocumentHandle} from '@sanity/sdk'
+import {expectTypeOf, test} from 'vitest'
+
+import {useDocument} from './useDocument'
+
+// End-to-end check that the resource-keyed lookup reaches the hook. The resolver reads
+// `SanitySchemasByResource`; this asserts `useDocument` passes the handle's project and
+// dataset through to it.
+//
+// Only covers the form where the literals are written at the call site. A handle built from
+// a selected resource, or arriving as a `DocumentHandle<'post'>` prop, still carries `string`
+// and resolves to nothing. That is the propagation work, tracked separately.
+
+type HookPost = {
+  _id: string
+  _type: 'post'
+  _createdAt: string
+  _updatedAt: string
+  _rev: string
+  title: string
+}
+interface ProductionPost extends Omit<HookPost, 'title'> {
+  title: number
+}
+
+// Registered the way generated files do: as globals, which the interfaces `@sanity/client`
+// exports extend. Every file in this package's type-check program sees these registrations, not
+// only this test, so their keys must stay unique across the package's tests.
+declare global {
+  interface SanitySchemasByResource {
+    'hook1.test': HookPost
+    'hook2.production': ProductionPost
+  }
+}
+
+const testHandle = createDocumentHandle({
+  projectId: 'hook1',
+  dataset: 'test',
+  documentId: 'a',
+  documentType: 'post',
+})
+const productionHandle = createDocumentHandle({
+  projectId: 'hook2',
+  dataset: 'production',
+  documentId: 'a',
+  documentType: 'post',
+})
+
+test('useDocument resolves the document type for each handle resource', () => {
+  expectTypeOf(useDocument(testHandle).data).toEqualTypeOf<HookPost | null>()
+  expectTypeOf(useDocument(productionHandle).data).toEqualTypeOf<ProductionPost | null>()
+})
+
+test('useDocument preserves the resource when selecting a field', () => {
+  expectTypeOf(useDocument({...testHandle, path: 'title'}).data).toEqualTypeOf<string | undefined>()
+  expectTypeOf(useDocument({...productionHandle, path: 'title'}).data).toEqualTypeOf<
+    number | undefined
+  >()
+})
+
+test('explicit resource generics require a matching handle', () => {
+  useDocument<'title', 'post', 'test', 'hook1'>({...testHandle, path: 'title'})
+  // @ts-expect-error The handle belongs to a different project and dataset.
+  useDocument<'title', 'post', 'test', 'hook1'>({...productionHandle, path: 'title'})
+})

package/src/hooks/document/useDocument.ts

@@ -61,7 +61,7 @@ interface UseDocument {
     TDataset extends string = string,
     TProjectId extends string = string,
   >(
-    options: UseDocumentOptions<TPath, TDocumentType>,
+    options: UseDocumentOptions<TPath, TDocumentType, TDataset, TProjectId>,
   ): {
     data: JsonMatch<ResolveDocument<TDocumentType, `${TProjectId}.${TDataset}`>, TPath> | undefined
   }
@@ -139,7 +139,7 @@ interface UseDocument {
     TDataset extends string = string,
     TProjectId extends string = string,
   >(
-    options: UseDocumentOptions<TPath, TDocumentType>,
+    options: UseDocumentOptions<TPath, TDocumentType, TDataset, TProjectId>,
   ): TPath extends string
     ? {
         data: