E2E verification + changesets for the docs plugin epic

未关闭
  • 哪里不对？
#448 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

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

调研方向

Start with the docs plugin work in blocked issue #447, then inspect existing browser specs under tests/regression/browser/ and the repository scripts for the typecheck, lint, and test commands. Add a browse-to-read-doc regression spec using data-testid selectors for chrome and verify the Playwright trace artifact. Done means the full quality gate passes and changesets cover every-plugin and the docs plugin package.

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

描述

ready-for-agent

Parent

#444

What to build

Close the epic out with the verification and release bookkeeping: a browser regression spec covering the user-observable path, the full quality gate, and changesets for every published package touched.

  • Browser spec under tests/regression/browser/ covering browse → read a doc: data-testid selectors only for chrome, ends with a verifiable Playwright trace artifact
  • Full pnpm run typecheck / lint / test green
  • Changesets for every-plugin (rspack plugin-append) and the new docs plugin package

Blocked by: #447

Acceptance criteria

  • Browser regression spec passes with a trace artifact committed by the run
  • pnpm run typecheck, lint, and test all green
  • Changesets present for every-plugin and the docs plugin package
主要语言
TypeScript
星标
5
派生
3
平均合并
9 小时 58 分钟
30 天内合并 PR
212

环境准备

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

从这里开始

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

NEARBuilders/everything-dev 的其他 Issue

查看 NEARBuilders/everything-dev 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

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