Deployment-status files follow #1994's decision on import extensions

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
25/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
typescript
领域
tooling

调研方向

Read issue #1994 first; this issue explicitly depends on its decision about import extensions. The affected entry point is src/features/instance/config/deployments/deploymentsSearch.ts, along with its tests. If #1994 calls for extensions, update these imports consistently with that decision; if it exempts Studio, close this issue without a code change.

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

描述

The deployment-status change (claude/funny-lalande-aa0067, Harper 5.4 rolling_out/partial) adds a local import without a file extension (@/lib/string/wasAReleasedBeforeB in src/features/instance/config/deployments/deploymentsSearch.ts), plus extensionless imports in its tests, which the Harper TypeStrip checklist asks for. They match every other import in src/, and adding .ts/.tsx fails tsc today because tsconfig.app.json doesn't set allowImportingTsExtensions.

So this follows #1994, which decides whether Studio adopts extensions or is exempt. Close this together with it: if Studio adopts them, these files move with the rest; if it's exempt, nothing changes here.

Review-Deferral: 170d0acf590d32d2 severity=nit category=maintainability

🤖 Generated by Claude Code (Claude Opus 5.5); posted via @dawsontoth.

主要语言
TypeScript
星标
5
派生
4
平均合并
1 天 12 小时
30 天内合并 PR
65

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

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

HarperFast/studio 的其他 Issue

查看 HarperFast/studio 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

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