[GabeSilvaDev]

Summary

An i18n meaning or description is written into the JSDoc comment above the Closure goog.getMsg message, as raw text. A */ in it ends the comment early, and whatever follows becomes code in the emitted module:

<img i18n-alt="*/ } steal(); if (0) { /*" alt="Logo" />

// before
if (((typeof ngI18nClosureMode !== "undefined") && ngI18nClosureMode)) {
  /** @desc */ } steal(); if (0) { /* */
  const MSG_C_TS__0 = goog.getMsg("Logo");
  (i18n_0 = MSG_C_TS__0);
} else {
  (i18n_0 = $localize `:*/ } steal(); if (0) { /*:Logo`);
}

The } closes the ngI18nClosureMode branch and if (0) { takes over the rest, so steal() runs every time the consts are built, not only in Closure mode, and the message still works. Other text after */ or /* breaks the output instead.

ngtsc never emits this: tagToString in output_ast.ts throws JSDoc text cannot contain "/*" and "*/" for such a text, and escapes @ as \@ so the text cannot start a JSDoc tag of its own.

This PR does both:

• An i18n or i18n-* meaning or description with /* or */ is reported as a template error with Angular's message, so the component is not compiled. The check runs where the attribute is parsed (html_to_r3.rs), because errors that pipeline phases push to job.diagnostics don't reach transform_angular_file's diagnostics today.
• @ in a meaning or description is emitted as \@ (/** @desc mail a\@b.c */).

Test plan

• test_i18n_meta_that_would_close_its_jsdoc_comment_is_an_error: */ in a description, in an i18n-alt meaning, and /* in a meaning are reported with that error and emit no JSDoc comment.
• test_i18n_meta_at_sign_is_escaped_in_jsdoc: @ in both texts is escaped.
• Removing either of the two checks, or the escaping, fails a test.
• cargo test --all-features, cargo fmt --all -- --check, and cargo run -p oxc_angular_conformance (1264/1264, snapshot unchanged).

Separately: compile_component_full collects job.diagnostics and drops them, so errors such as Unsupported expression in two-way action binding ([(x)]="a + b", which ngtsc rejects) are not reported either. Returning them as compile_template_for_hmr already does also surfaces a false AssertionError: unable to find a dependency function for this deferred block for @defer (on viewport(missing)), which ngtsc accepts, and fails 18 existing defer tests. So that is left out of this PR.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	🔄 Running since 2026-10-28T03:35:38.725276Z	a85febf	Manual request

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota.

An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing. Review the Copilot code review billing settings.

[GabeSilvaDev]

@codex review

[chatgpt-codex-connector]

Codex Review: Something went wrong. Try again later by commenting “@codex review”.

An unknown error occurred

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[Brooooooklyn]

@codex review