Skip to content

Update error message links to versioned docs#66374

Closed
SkyZeroZx wants to merge 7 commits intoangular:mainfrom
SkyZeroZx:update-docs-version-msg
Closed

Update error message links to versioned docs#66374
SkyZeroZx wants to merge 7 commits intoangular:mainfrom
SkyZeroZx:update-docs-version-msg

Conversation

@SkyZeroZx
Copy link
Copy Markdown
Contributor

@SkyZeroZx SkyZeroZx commented Jan 7, 2026

Align error message links with versioned documentation.
Add the following commits :

  • core: update error message links to versioned docs
  • compiler-cli: update error message links to versioned docs

PR Checklist

Please check if your PR fulfills the following requirements:

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Documentation content changes
  • angular.dev application / infrastructure changes
  • Other... Please describe:

What is the current behavior?

Issue Number: #44650

What is the new behavior?

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

@pullapprove pullapprove bot requested review from JeanMeche and JoostK January 7, 2026 20:30
@angular-robot angular-robot bot added area: compiler Issues related to `ngc`, Angular's template compiler area: core Issues related to the framework runtime labels Jan 7, 2026
@ngbot ngbot bot added this to the Backlog milestone Jan 7, 2026
Comment on lines +12 to +13
const versionSubDomain = VERSION.major !== '0' ? `v${VERSION.major}.` : '';
return `https://${versionSubDomain}angular.dev`;
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should also be able to link to next.angular.dev if the version have next/rc.

Copy link
Copy Markdown
Contributor Author

@SkyZeroZx SkyZeroZx Jan 7, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I’ll try . I kept it as-is because, if I’m not mistaken, changing it would require updating some unit tests.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated, now supports linking to next.angular.dev, update the respective tests

@SkyZeroZx SkyZeroZx force-pushed the update-docs-version-msg branch from 1e7bce3 to 7909500 Compare January 7, 2026 20:33
Error message links now point to the archived documentation site (v*.angular.dev)
so that referenced content matches the framework version in use.

See angular#44650
Error message links now point to the archived documentation site (v*.angular.dev)
so that referenced content matches the framework version in use.

See angular#44650
@SkyZeroZx SkyZeroZx force-pushed the update-docs-version-msg branch from 7909500 to 774388b Compare January 7, 2026 21:21
@SkyZeroZx
Copy link
Copy Markdown
Contributor Author

SkyZeroZx commented Jan 7, 2026

I also see that this change affects the forms/common tests, I’m going to update the other unit tests as well.

@thePunderWoman
Copy link
Copy Markdown
Contributor

thePunderWoman commented Jan 9, 2026

caretaker note: This requires an update to a g3patch. You'll need to land cl/854258398 before this.

Copy link
Copy Markdown
Contributor

@thePunderWoman thePunderWoman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@thePunderWoman thePunderWoman added action: merge The PR is ready for merge by the caretaker target: patch This PR is targeted for the next patch release merge: caretaker note Alert the caretaker performing the merge to check the PR for an out of normal action needed or note labels Jan 9, 2026
thePunderWoman pushed a commit that referenced this pull request Jan 9, 2026
Error message links now point to the archived documentation site (v*.angular.dev)
so that referenced content matches the framework version in use.

See #44650

PR Close #66374
thePunderWoman pushed a commit that referenced this pull request Jan 9, 2026
…66374)

Error message links now point to the archived documentation site (v*.angular.dev)
so that referenced content matches the framework version in use.

See #44650

PR Close #66374
thePunderWoman pushed a commit that referenced this pull request Jan 9, 2026
Error message links now point to the archived documentation site (v*.angular.dev)
so that referenced content matches the framework version in use.

See #44650

PR Close #66374
thePunderWoman pushed a commit that referenced this pull request Jan 9, 2026
…66374)

Error message links now point to the archived documentation site (v*.angular.dev)
so that referenced content matches the framework version in use.

See #44650

PR Close #66374
@thePunderWoman
Copy link
Copy Markdown
Contributor

This PR was merged into the repository. The changes were merged into the following branches:

thePunderWoman pushed a commit that referenced this pull request Jan 9, 2026
…66374)

Error message links now point to the archived documentation site (v*.angular.dev)
so that referenced content matches the framework version in use.

See #44650

PR Close #66374
@angular-automatic-lock-bot
Copy link
Copy Markdown

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Feb 9, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

action: merge The PR is ready for merge by the caretaker area: compiler Issues related to `ngc`, Angular's template compiler area: core Issues related to the framework runtime merge: caretaker note Alert the caretaker performing the merge to check the PR for an out of normal action needed or note target: patch This PR is targeted for the next patch release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants