Lovable: activity and route are picked by two independent lookups

未关闭
#746 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
半天
新手友好度
66/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
typescript
领域
backend

调研方向

Start at src/server/providers/adapters/lovable.ts around lines 105-107, where activity and route are each resolved by a separate find over the listing's surfaces; read what a surface entry carries to see how one lookup can yield both. Then read the synced-routes strip in poll-models.ts, which only compares activity on the stored-routes path, to see where the two paths must agree. Done looks like a test with a mixed-surface listing row (e.g. ['live','chat-completions']) that no longer binds a route of the other activity.

由索引模型根据 Issue 内容生成。

描述

Problem

src/server/providers/adapters/lovable.ts (around lines 105-107) picks a row's activity and its route with two independent finds over the listing's surfaces, and the synced-routes strip in poll-models.ts compares activity only on the stored-routes path. A listing such as ['live','chat-completions'] would bind an audio row to chat/completions, and its schema link would 404. Zero cases today (found in the review of #737).

Ask

Derive activity and route from the same surface, or throw when they disagree.

Acceptance

  • A test with a mixed-surface listing row does not bind a route of another activity.
主要语言
TypeScript
星标
0
派生
1
平均合并
5 小时 40 分钟
30 天内合并 PR
193

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

TanStack/schemas 的其他 Issue

查看 TanStack/schemas 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。