feat(setup): the datasource list shows the real connect verdict, with the operator-facing reason (framework#3827) - #2926
Merged
Conversation
… the operator-facing reason (framework#3827)
The framework's datasource-admin list now reports a four-state `status` from
the retained connect verdict — ok | error | blocked | unvalidated — plus an
operator-facing `statusReason` (framework#3827/#3869), and since framework#3869
the primary `default` datasource appears in the list too. The page rendered
`status` as an undifferentiated text fragment ("· error"), so a dead datasource
read exactly like an untested one and the reason never surfaced.
- Status chip per verdict: connected (emerald) / connect failed (destructive) /
blocked by policy (amber) / not connected (muted). Unknown values fall back
to a muted chip with the raw string, so a future framework state degrades
readably instead of disappearing.
- `statusReason` shows under the row for error/blocked (truncated, full text
via the native title tooltip — the file's existing idiom). This surface is
admin-gated; end users never see these strings (framework#3828).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TQVM3A9Yd6N2eZS8ZcdnMk
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
Contributor
✅ Console Performance Budget
📦 Bundle Size Report
Size Limits
|
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
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.
framework 侧 #3827/#3869 之后,datasource-admin 列表返回四态
status(留存的连接判决)+ 面向运维的statusReason,且主库default也进入列表。本页此前把status渲染成无区分的裸文本(· error),死掉的 datasource 和没测过的看起来一模一样,reason 从不显示 —— 后端说了真话、界面不显示,framework#3827 的价值只兑现了一半。改动(单文件:
DatasourceResourcePage.tsx)connected(emerald)/connect failed(destructive)/blocked by policy(amber)/not connected(muted)。未知值降级为 muted chip 显示原始字符串 —— framework 未来加状态时页面可读地降级,而不是消失。statusReason在 error / blocked 行下方显示(截断,完整文本走原生titletooltip —— 本文件既有惯例,不引新依赖)。该表面已有 admin 门禁,展示原始原因是设计意图;终端用户永远看不到这些字符串(framework#3828 的 privileged/public 分离)。unvalidated保持视觉安静 —— 它的含义是「一无所知」,不是「有问题」。验证
@object-ui/app-shelltype-check 0 错、测试 91/91、lint 0 错(1986 条 warning 为仓库既有基线)。pnpm build全 workspace 43/43 通过。合并后需要在 framework 仓库跑
pnpm objectui:refresh把构建拉进packages/console/。Generated by Claude Code