@maple-dev/alchemy: typed dashboard props, a managed refresh interval, and adopting a dashboard built in the UI
维护者通常 1 天内回复
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 18/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- typescript
调研方向
Start with the @maple-dev/alchemy provider and its Dashboard, DashboardWidget, and DashboardData types; compare them with the v2 API schema for visualizations, raw_sql sources, layout, and refresh_interval_seconds. The linked open pull request #1872 is the implementation path, so read its diff and related tests rather than starting independently. Done means the typed props, managed refresh interval, and dashboardId adoption behavior are covered by tests and the provider no longer creates a duplicate dashboard when Alchemy state is absent.
由索引模型根据 Issue 内容生成。
描述
Written by an AI agent (Claude) on behalf of @jasonkuhrt.
A team managing its Maple dashboards with @maple-dev/alchemy can't type-check a dashboard, can't manage its refresh interval, and can't take over a dashboard someone already built in the UI.
yield* Maple.Dashboard("service-health", {
name: "Service health",
// Type error: not a prop, though the v2 API has it.
refresh_interval_seconds: 60,
widgets: [
// Type-checks, then the API answers 400 at deploy: "timeseries" is not a
// visualization, and a raw_sql source needs its `sql`.
{ id: "requests", visualization: "timeseries", data_source: { kind: "raw_sql" } },
],
})
And declaring a dashboard that was first built in the UI creates a second one beside it, because the provider creates whenever it has no Alchemy state.
What we'd like to write instead:
// Panels as values, checked where they're written, shared across dashboards.
const requests = Maple.DashboardWidget.make({
id: "requests",
visualization: "stat",
data_source: { kind: "raw_sql", sql: "SELECT count() AS value FROM traces WHERE $__orgFilter" },
display: { title: "Requests" },
layout: { x: 0, y: 0, w: 3, h: 4 },
})
yield* Maple.Dashboard("service-health", {
...Maple.DashboardData.make({ name: "Service health", refresh_interval_seconds: 60, widgets: [requests] }),
// Take over the dashboard built in the UI.
dashboardId: "dash_…",
})
Heartbeat runs this today through a patch of @maple-dev/alchemy 0.2.4, for two dashboards. #1872 implements it.
- 主要语言
- TypeScript
- 星标
- 1.8k
- 派生
- 120
- 平均合并
- 8 小时 11 分钟
- 30 天内合并 PR
- 667
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
MapleTechLabs/maple 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
MapleTechLabs/maple#1921 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 74/100
MapleTechLabs/maple#1888 ·
维护者通常 1 天内回复
-
Alerting: Linear as a destination type, opening one issue per incident可能已有人在做 @Makisuo 于 1 天前认领。 未关闭
难度 5/5 一周以上 新手友好度 20/100
MapleTechLabs/maple#1896 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 42/100
MapleTechLabs/maple#1874 ·
维护者通常 1 天内回复
-
难度 3/5 1-2 天 新手友好度 68/100
MapleTechLabs/maple#1873 ·
维护者通常 1 天内回复
查看 MapleTechLabs/maple 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 65/100
lichess-org/lila#22324 · 1 条评论 ·
维护者通常 1 天内回复
-
ep:WebGPU platform:web quantization
难度 2/5 1-3 小时 新手友好度 66/100
microsoft/onnxruntime#33752 ·
维护者通常 2 天内回复
-
[Skill Bug]: entra-agent-id: inaccurate blueprint permission inheritance and parent token sub claim未关闭bug entra-agent-id
难度 2/5 1-3 小时 新手友好度 78/100
microsoft/GitHub-Copilot-for-Azure#3467 · 1 条评论 ·
维护者通常 1 天内回复
-
fix(worker): keep normal prepare waiting states failure-free可能已有人在做 @LichKing-2234 今天认领。 未关闭agent:codex priority:P1
难度 2/5 1-3 小时 新手友好度 72/100
AgoraIO-Extensions/agent-infra#3745 ·
维护者通常 1 天内回复
-
The five-line work window can drop its oldest line: the per-line byte share ignores the JSON framing可能已有人在做 @Eapp1e 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 84/100
makecindy/cindy#7973 · 1 条评论 ·
维护者通常 1 天内回复