orpc-contract-first

Contract-first API patterns for Dify frontend using oRPC with TanStack Query integration. - Define contracts in web/contract/* as single source of truth; consume via useQuery(consoleQuery.xxx.queryOptions(...)) at call sites for 1:1 endpoint mappings - Use .key() for partial matching in invalidation/refetch, .queryKey() for specific query identity, and .mutationKey() for mutation defaults or status filtering - Extract queryOptions helpers only when 3+ call sites share identical options; create use-* hooks only for multi-query orchestration or domain-level derived state - Follow input structure { params, query?, body? } in contracts; omit .input(...) for GET endpoints without input; group router nesting by API prefix - Keep contract as single source of truth in web/contract/* . - Default query usage: call-site useQuery(consoleQuery|marketplaceQuery.xxx.queryOptions(...)) when endpoint behavior maps 1:1 to the contract. - Keep abstractions minimal and preserve TypeScript inference. - Define contract in web/contract/console/{domain}.ts or web/contract/marketplace.ts - Use base.route({...}).output(type ()) as baseline. - Add .input(type ()) only when request has params/query/body . - For GET without input, omit .input(...) (do not use .input(type ()) ). - Register contract in web/contract/router.ts - Import directly from domain files and nest by API prefix.