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

e2e compare: setClassMetadata extraction regex never matches (ɵɵ vs ɵ) — classMetadataDiffs is dead code

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

维护者通常 1 天内回复

已经有一个关联 PR 被合并了。

  • #562 来自 @Brooooooklyn —— 已合并

评估

难度
4/5
预计耗时
3-5 天
新手友好度
38/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
rust
领域
testing-qa

调研方向

Start in src/compare.ts at extractClassMetadataCalls (around line 2328) and normalizeMetadataString, then run the e2e compare harness to inspect the 79 surfaced fixture mismatches. Fixing the regex and normalization is only the start: classify residual diffs as real emit bugs or noise, and update KnownDifference per fixture, including edge-cases/aliased-injectable. Done means class metadata diffs are detected, allowlisted explicitly where appropriate, and the comparison passes without hiding real mismatches.

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

描述

The e2e compare harness never actually compares setClassMetadata: extractClassMetadataCalls (src/compare.ts:2328) matches i\d+\.ɵɵsetClassMetadata but both compilers emit i0.ɵsetClassMetadata (single ɵ), so classMetadataDiffs is always empty and testFixture's known-difference gate never sees them.

Correcting the regex surfaces 79 fixture mismatches. Sampling shows most are normalization noise — same decorator payloads differing in quote style, indentation and trailing commas — so normalizeMetadataString needs to be made syntax-insensitive (e.g. parse and compare the AST or normalize quotes/commas) before the check can be enabled.

Steps: fix the regex, strengthen normalizeMetadataString, triage the residual diffs (real emit bugs vs. remaining noise), and extend KnownDifference to allowlist classMetadataDiffs per fixture — the new edge-cases/aliased-injectable entry should then declare its extra setClassMetadata explicitly.

Surfaced by a Codex review comment on #560.

主要语言
Rust
星标
235
派生
21
平均合并
1 天 15 小时
30 天内合并 PR
65

环境准备

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

从这里开始

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

voidzero-dev/oxc-angular-compiler 的其他 Issue

查看 voidzero-dev/oxc-angular-compiler 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

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