From 696a9b01ef01c6ab6d83cf846a4b7b8dc6b5568c Mon Sep 17 00:00:00 2001 From: Ajit Singh Date: Thu, 6 Aug 2020 09:16:38 +0530 Subject: [PATCH] docs: remove https://angular.io from internal links (#38360) PR #36601 introduces icons on all links if the link contains https:// or http:// but there were some internal links left which contained https://angular.io. Removed https://angular.io from all these links. PR Close #38360 --- aio/content/guide/architecture-components.md | 4 ++-- aio/content/guide/built-in-directives.md | 2 +- aio/content/guide/cli-builder.md | 2 +- aio/content/guide/i18n.md | 6 +++--- aio/content/guide/roadmap.md | 4 ++-- 5 files changed, 9 insertions(+), 9 deletions(-) diff --git a/aio/content/guide/architecture-components.md b/aio/content/guide/architecture-components.md index c4f8e7f9de..bedc446a51 100644 --- a/aio/content/guide/architecture-components.md +++ b/aio/content/guide/architecture-components.md @@ -124,9 +124,9 @@ Data binding plays an important role in communication between a template and its Angular pipes let you declare display-value transformations in your template HTML. A class with the `@Pipe` decorator defines a function that transforms input values to output values for display in a view. -Angular defines various pipes, such as the [date](https://angular.io/api/common/DatePipe) pipe and [currency](https://angular.io/api/common/CurrencyPipe) pipe; for a complete list, see the [Pipes API list](https://angular.io/api?type=pipe). You can also define new pipes. +Angular defines various pipes, such as the [date](api/common/DatePipe) pipe and [currency](api/common/CurrencyPipe) pipe; for a complete list, see the [Pipes API list](api?type=pipe). You can also define new pipes. -To specify a value transformation in an HTML template, use the [pipe operator (|)](https://angular.io/guide/template-expression-operators#pipe). +To specify a value transformation in an HTML template, use the [pipe operator (|)](guide/template-expression-operators#pipe). `{{interpolated_value | pipe_name}}` diff --git a/aio/content/guide/built-in-directives.md b/aio/content/guide/built-in-directives.md index f1a65922a3..d1a954169d 100644 --- a/aio/content/guide/built-in-directives.md +++ b/aio/content/guide/built-in-directives.md @@ -140,7 +140,7 @@ Angular provides *value accessors* for all of the basic HTML form elements and t You can't apply `[(ngModel)]` to a non-form native element or a third-party custom component until you write a suitable value accessor. For more information, see -the API documentation on [DefaultValueAccessor](https://angular.io/api/forms/DefaultValueAccessor). +the API documentation on [DefaultValueAccessor](api/forms/DefaultValueAccessor). You don't need a value accessor for an Angular component that you write because you can name the value and event properties diff --git a/aio/content/guide/cli-builder.md b/aio/content/guide/cli-builder.md index 054a50b840..166115ec39 100644 --- a/aio/content/guide/cli-builder.md +++ b/aio/content/guide/cli-builder.md @@ -46,7 +46,7 @@ For example, your `myBuilder` folder could contain the following files. | `package.json` | Dependencies. See https://docs.npmjs.com/files/package.json. | | `tsconfig.json` | [TypeScript configuration](https://www.typescriptlang.org/docs/handbook/tsconfig-json.html). | -You can publish the builder to `npm` (see [Publishing your Library](https://angular.io/guide/creating-libraries#publishing-your-library)). If you publish it as `@example/my-builder`, you can install it using the following command. +You can publish the builder to `npm` (see [Publishing your Library](guide/creating-libraries#publishing-your-library)). If you publish it as `@example/my-builder`, you can install it using the following command. diff --git a/aio/content/guide/i18n.md b/aio/content/guide/i18n.md index db0162408f..ba0d175262 100644 --- a/aio/content/guide/i18n.md +++ b/aio/content/guide/i18n.md @@ -58,7 +58,7 @@ While following these steps, you can [explore the translated example app](#app-p The following are optional practices that may be required in special cases: -* [Set the source locale manually](#set-source-manually) if you need to set the [LOCALE_ID](https://angular.io/api/core/LOCALE_ID "API reference for LOCALE_ID") token. +* [Set the source locale manually](#set-source-manually) if you need to set the [LOCALE_ID](api/core/LOCALE_ID "API reference for LOCALE_ID") token. * [Import global variants of the locale data](#import-locale) for extra locale data. * [Manage marked text with custom IDs](#custom-id) if you require more control over matching translations. @@ -77,7 +77,7 @@ This command updates your project's `package.json` and `polyfills.ts` files to i
-For more information about `package.json` and polyfill packages, see [Workspace npm dependencies](https://angular.io/guide/npm-packages). +For more information about `package.json` and polyfill packages, see [Workspace npm dependencies](guide/npm-packages).
@@ -804,7 +804,7 @@ The following tabs show the example app and its translation files: The following are optional practices that may be required in special cases: -* [Set the source locale manually](#set-source-manually) by setting the [LOCALE_ID](https://angular.io/api/core/LOCALE_ID "API reference for LOCALE_ID") token. +* [Set the source locale manually](#set-source-manually) by setting the [LOCALE_ID](api/core/LOCALE_ID "API reference for LOCALE_ID") token. * [Import global variants of the locale data](#import-locale) for extra locale data. * [Manage marked text with custom IDs](#custom-id) if you require more control over matching translations. diff --git a/aio/content/guide/roadmap.md b/aio/content/guide/roadmap.md index 454320f116..1cc7eb356f 100644 --- a/aio/content/guide/roadmap.md +++ b/aio/content/guide/roadmap.md @@ -20,7 +20,7 @@ To ensure we provide a future-proof e2e testing strategy, we want to evaluate th ### Angular libraries use Ivy -We are investing in the design and development of Ivy library distribution plan, which will include an update of the library package format to use Ivy compilation, unblock the deprecation of the View Engine library format, and [ngcc](https://angular.io/guide/glossary#ngcc). +We are investing in the design and development of Ivy library distribution plan, which will include an update of the library package format to use Ivy compilation, unblock the deprecation of the View Engine library format, and [ngcc](guide/glossary#ngcc). ### Evaluate future RxJS changes (v7 and beyond) @@ -72,7 +72,7 @@ We want to unify commit message requirements and conformance across Angular repo We are going to design and implement a plan to make Zone.js optional from Angular applications. This way, we will simplify the framework, improve debugging, and reduce application bundle size. Additionally, this will allow us to take advantage of native async/await syntax, which currently Zone.js does not support. -### Remove legacy [View Engine](https://angular.io/guide/ivy) +### Remove legacy [View Engine](guide/ivy) After the transition of all our internal tooling to Ivy has completed, we want to remove the legacy View Engine for smaller Angular conceptual overhead, smaller package size, lower maintenance cost, and lower complexity of the codebase.