Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Enable typed linting (typescript-eslint recommendedTypeChecked)

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

维护者通常 2 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
43/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
eslint, typescript
领域
testing, tooling

调研方向

Start by reviewing the ESLint configuration and the TypeScript project configuration, especially coverage for e2e/** and drizzle.config.ts; the issue does not name their paths. Then measure the findings for the proposed rules and split the rollout into the listed steps. Done means an agreed rule set is enabled with project service configured for .ts files and the required paths covered.

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

描述

Follow-up from #344. Running with recommendedTypeChecked produced about 1,000 findings, too many for one change.

Measured on main (2026-10-26), after removing noise from the trial config:

Rule Findings
no-unsafe-member-access / -assignment / -call / -return / -argument ~580
require-await 174
no-unnecessary-type-assertion 113
only-throw-error 98 (nearly all SvelteKit throw redirect() / error(), fixed by its allow option)
unbound-method 51
no-floating-promises 30
await-thenable 19
no-misused-promises 17
no-base-to-string 9

Prerequisites:

  • parserOptions.projectService for .ts files, not only Svelte files.
  • A tsconfig that covers e2e/** and drizzle.config.ts. Today the project service can't find them.
  • Lint time goes from about 36 s to about 55 s.

Proposed rollout, one PR per step:

  1. Turn on the rules that catch real bugs: no-floating-promises, no-misused-promises, await-thenable, and only-throw-error with a SvelteKit allow entry.
  2. no-unnecessary-type-assertion and require-await (mostly autofixable or mechanical).
  3. Decide whether to adopt the no-unsafe-* family at all, and how much of it, given how many hits come from untyped JSON and test code.
主要语言
TypeScript
星标
1
派生
0
平均合并
3 天 22 小时
30 天内合并 PR
34

环境准备

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

从这里开始

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

stackabletech/cockpit 的其他 Issue

查看 stackabletech/cockpit 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

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