Skip to content

chore: update origin to 4d985a179e (Angular v22.1.1) - #1197

Open
lacolaco wants to merge 59 commits into
angular:mainfrom
lacolaco:update-origin-4d985a179e
Open

chore: update origin to 4d985a179e (Angular v22.1.1)#1197
lacolaco wants to merge 59 commits into
angular:mainfrom
lacolaco:update-origin-4d985a179e

Conversation

@lacolaco

@lacolaco lacolaco commented Aug 8, 2026

Copy link
Copy Markdown
Collaborator

Summary

Sync angular-ja with upstream angular/angular @ 4d985a179e.

Target selection: the release tag 22.1.0 was not the commit serving production. angular.dev reports v22.1.1+sha-4d985a1 in its footer, so this PR syncs to that commit (4d985a179e, on the 22.1.x branch), consistent with how v22.0.0 was synced to fa546f382d rather than the tag.

Scope

88 markdown files and 4 source files were updated against the new upstream English.

Rebased onto main after #1174 and #1176 merged. guide/aria/combobox was newly translated by #1176; its translation is kept and only its ## APIs section was migrated to match, the same change applied to the other aria pages here. tutorials/first-app/steps/05-inputs from #1174 needed no change.

Notable content changes:

  • guide/aria/* (12 pages): upstream replaced the hand-written ## APIs tables with a compact ## API reference link list
  • reference/releases: release cadence updated (12-month major cycle, 24-month support window, v22.1 to v23.0 schedule)
  • app/features/update/recommendations: 4 new migration steps translated, plus http: to https: link corrections
  • guide/directives/structural-directives: the <docs-workflow> scaffold was consolidated into a single example, and the section was retranslated
  • reference/roadmap: in-progress entries moved into "Completed projects", with previously translated completed entries preserved
  • app/routing/navigation-entries: navigation badges refreshed and the new Signal Forms pages registered

Removed / moved pages

None. Every .en.* file in adev-ja/ (309) still has an upstream counterpart, and upstream deleted no localized page in this range.

Untranslated / deferred

New pages copied untranslated:

  • guide/forms/signals/dynamic-forms-with-json.md
  • guide/forms/signals/testing.md
  • reference/errors/NG0318.md, NG02825.md, NG05101.md, NG05102.md, NG05201.md, NG05703.md

Pages rewritten upstream past the point where the prior translation could be adapted. These are reset to upstream English, with the previous translation kept as .md.bak for re-translation:

  • ai/mcp-server-setup.md: IDE-specific sections removed, "Common Workflows" added
  • guide/directives/attribute-directives.md: three sections deleted upstream
  • guide/directives/overview.md: NgClass/NgStyle content removed upstream

Pages where the existing translation was kept and newly added upstream sections were inserted as untranslated English, pending follow-up translation:

guide/components/inputs, guide/directives/directive-composition-api, guide/forms/signals/custom-controls, guide/forms/signals/field-state-management, guide/signals/linked-signal, guide/signals/resource, guide/ssr, guide/templates/pipes, guide/testing/attribute-directives, introduction/essentials/signal-forms

Anchor IDs on translated headings

v22.1 adds a link validator to the API docs rendering pipeline. It resolves every guide link carrying a fragment against the anchors the target page actually exposes, and the build now fails on the first unresolved one. A Japanese heading without an explicit {#id} generates an ID from its Japanese text, so 42 links coming from upstream JsDoc stopped resolving.

These links were already unresolvable before this sync. The validator is what is new, so the breakage surfaces here.

Fixed by adding 153 explicit anchor IDs across 19 pages, each derived from the English heading at the same line index. One pre-existing anchor in guide/security.md was corrected from #sanitization-and-security-context to the plural form the English heading produces. Nothing else in these pages changed, and line counts are unaffected.

Incidental fixes

Three pre-existing defects were found in files inside the sync scope and repaired so that the Japanese pages line up with their English sources again. None were introduced by this sync:

  • guide/testing/attribute-directives.md: a closing ``` fence was missing, leaving a code block unterminated
  • guide/components/inputs.md: legacy <docs-code language="ts"> wrapper where upstream uses a fenced block
  • best-practices/style-guide.md: paragraph line wrapping was offset by one line against the English source, with the text itself unchanged

Test plan

  • pnpm test, all 9 localization patches (12 target files) apply to the new origin
  • pnpm lint
  • Line-count and structural-marker parity checked for all 308 .en.* / translated pairs
  • Fenced code-block content verified identical between English and Japanese for all 88 changed files
  • No backtick identifier removed upstream remains on the Japanese side
  • All 360 guide links with a fragment resolve against the anchors the Japanese pages expose
  • indexName: 'angular_jp_v19' fixed value preserved in replace-environment-values.patch

@lacolaco
lacolaco force-pushed the update-origin-4d985a179e branch from 6162645 to 3bdb071 Compare August 8, 2026 13:42
lacolaco added 29 commits August 8, 2026 22:54
lacolaco added 28 commits August 8, 2026 22:54
…n-angular/steps/19-creating-an-injectable-service
…ials/signals/steps/7-using-signals-with-services
@lacolaco
lacolaco force-pushed the update-origin-4d985a179e branch from 3bdb071 to bfe5410 Compare August 8, 2026 13:59
Angular v22.1 adds a link validator to the API docs rendering pipeline
(validateGuideUrl). It resolves every guide link with a fragment against
the anchors the page actually exposes. Japanese headings without an
explicit {#id} generate a Japanese-text ID, so 42 links from upstream
JsDoc no longer resolved and the build failed.

Anchor IDs are derived from the English heading at the same line index.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant