feat(spec)!: 移除从未实现的 GraphQL 面 — 不在产品计划 (#2462 后续) - #3562
Merged
Conversation
…ow-on) Product decision: GraphQL is not on the plan. It was schema-only from day one — 20+ spec config schemas, an unconditionally-501 handleGraphQL (kernel.graphql never assigned in the monorepo), and THREE separate mounts (dispatcher if-chain, dispatcher-plugin hono route, hono adapter) advertising the dead endpoint: the "declared ≠ mounted ≠ implemented" seam disease in one picture. Removed: spec schemas/contracts/enum members (CoreServiceName, ApiProtocolType, query dialects, graphql-playground), capability booleans, discovery/router fields, all three runtime mounts, the discovery advertisement, plugin-dev stubs, the now-dead resolveRequestExecutionContext, qa conformance rows + ratchet pins + dogfood surface cases, generated JSON-schema manifest keys + reference docs, and handwritten doc mentions. Kept deliberately: external-datasource 'graphql' protocol option (third parties may speak GraphQL to us as a CLIENT) and cloud's reserved slug. objectui's own dead 'graphql' union member noted for cross-repo cleanup. Verified: full monorepo build+test forced, 131 tasks green (spec 6675, core 386, runtime 647, dogfood 60, conformance 41 among them); api-surface + json-schema manifest + reference docs regenerated. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub. 1 Skipped Deployment
|
github-actions
Bot
added
documentation
Contributor
📓 Docs Drift CheckThis PR changes 8 package(s): 123 hand-written doc(s) reference the affected code and may need an implementation-accuracy re-verification:
|
…phQL removal follow-through) - Changeset major → minor per the launch-window convention (the gate's own instruction; same treatment as #3486/#2377 — breaking rides minor without burning the whole fixed group's major). - Drop the api/graphql.zod.ts entry from the skill-references mapping and regenerate (check:skill-refs gate). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This was referenced Jul 27, 2026
os-zhuang
added a commit
that referenced
this pull request
Jul 27, 2026
…xture debris (#3586) (#3595) The const described a route surface that never existed (/workflow, /realtime listed; eight real prefixes missing) and was consumed by nothing in the runtime — only its own tests and api-surface.json. Its one real-world effect was underwriting CLIENT_SPEC_COMPLIANCE.md's false "FULLY COMPLIANT" verdict (retired in #3571). The maintained, guard-enforced source of truth is packages/runtime/src/route-ledger.ts. Since the major train is loading now (#3562, #3581), the removal ships directly instead of the deprecate-first interim step. Also swept what #3562 left behind: registry test fixtures renamed from graphql_api//graphql to honest OData naming, the tautological config.graphql assertions dropped, the stale '"type": "graphql"' JSDoc example corrected. Client's bare tsc -p is verified clean (the TS2741 acceptance item — resolved by #3562's schema change, confirmed here). Closes #3586 Claude-Session: https://claude.ai/code/session_01LX9ut3MK3KykE11S9bJmv5 Co-authored-by: Claude <noreply@anthropic.com>
This was referenced Jul 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
决策背景
用户拍板：GraphQL 不在开发计划中，相关代码和文档直接删除。
现状证据（与记忆/审计一致）：GraphQL 自始至终 schema-only——spec 里 20+ 配置 schema（type/query/mutation/subscription/resolver/federation/persisted-query/rate-limit…）、
handleGraphQL恒 501（kernel.graphql在 monorepo 从未被赋值）、三处挂载各自广告这个死端点（dispatcher if 链、dispatcher-plugin hono 路由、hono adapter）——"declared ≠ mounted ≠ implemented" 缝病的完整标本。删除面
api/graphql.zod.ts+contracts/graphql-service.ts整删；CoreServiceName/ApiProtocolType/查询方言/graphql-playground枚举成员删；graphqlApi+network capability 布尔、discovery/router 路由字段删。BREAKING（照 feat(spec)!: prune dead ReportColumnSchema/ReportGroupingSchema exports + unread report chart groupBy (#3463) #3488 先例 major）。handleGraphQL、if 链分支、两处 hono 挂载、discovery 广告、连带死亡的resolveRequestExecutionContext全删。有意保留
'graphql'协议选项——第三方系统可能以 GraphQL 对外，我们作为客户端连它是合法场景。'graphql'联合成员 → 跨仓清理项（不阻塞本 PR）。行为变化
POST /graphql从恒 501 变 404（诚实状态：面不存在）；匿名拒绝矩阵少两行（surface 消失非放开）。验证
全 monorepo build+test 强制无缓存 131 任务全绿（spec 6675 / core 386 / runtime 647 / dogfood 60 / conformance 41 在内）。
关联 #2462。
🤖 Generated with Claude Code