From cce9f73c5464f6c603af91f8e0231c670884b68d Mon Sep 17 00:00:00 2001 From: Sean Perkins Date: Tue, 30 May 2023 14:39:19 -0400 Subject: [PATCH 1/4] chore: prettier formatting --- docs/angular/navigation.md | 4 ---- versioned_docs/version-v5/angular/navigation.md | 4 ---- 2 files changed, 8 deletions(-) diff --git a/docs/angular/navigation.md b/docs/angular/navigation.md index eb05502309c..9ad675058a0 100644 --- a/docs/angular/navigation.md +++ b/docs/angular/navigation.md @@ -118,10 +118,6 @@ export class LoginComponent { Both options provide the same navigation mechanism, just fitting different use cases. -:::note -A note on navigation with relative URLs: Currently, to support multiple navigation stacks, relative URLs are something not supported -::: - ### Navigating using LocationStrategy.historyGo Angular Router has a [LocationStrategy.historyGo](https://angular.io/api/common/LocationStrategy#historyGo) method that allows developers to move forward or backward through the application history. Let's take a look at an example. diff --git a/versioned_docs/version-v5/angular/navigation.md b/versioned_docs/version-v5/angular/navigation.md index 0e5148442b8..9dcbcc88949 100644 --- a/versioned_docs/version-v5/angular/navigation.md +++ b/versioned_docs/version-v5/angular/navigation.md @@ -109,10 +109,6 @@ export class LoginComponent { Both options provide the same navigation mechanism, just fitting different use cases. -:::note -A note on navigation with relative URLs: Currently, to support multiple navigation stacks, relative URLs are something not supported -::: - ## Lazy loading routes Now the current way our routes are setup makes it so they are included in the same chunk as the root app.module, which is not ideal. Instead, the router has a setup that allows the components to be isolated to their own chunks. From 40f53c284b8bc033c14038fea67554a875ce4f63 Mon Sep 17 00:00:00 2001 From: Sean Perkins Date: Tue, 30 May 2023 15:14:50 -0400 Subject: [PATCH 2/4] chore: revert invalid changes --- docs/angular/navigation.md | 4 ++++ versioned_docs/version-v5/angular/navigation.md | 4 ++++ 2 files changed, 8 insertions(+) diff --git a/docs/angular/navigation.md b/docs/angular/navigation.md index 9ad675058a0..eb05502309c 100644 --- a/docs/angular/navigation.md +++ b/docs/angular/navigation.md @@ -118,6 +118,10 @@ export class LoginComponent { Both options provide the same navigation mechanism, just fitting different use cases. +:::note +A note on navigation with relative URLs: Currently, to support multiple navigation stacks, relative URLs are something not supported +::: + ### Navigating using LocationStrategy.historyGo Angular Router has a [LocationStrategy.historyGo](https://angular.io/api/common/LocationStrategy#historyGo) method that allows developers to move forward or backward through the application history. Let's take a look at an example. diff --git a/versioned_docs/version-v5/angular/navigation.md b/versioned_docs/version-v5/angular/navigation.md index 9dcbcc88949..0e5148442b8 100644 --- a/versioned_docs/version-v5/angular/navigation.md +++ b/versioned_docs/version-v5/angular/navigation.md @@ -109,6 +109,10 @@ export class LoginComponent { Both options provide the same navigation mechanism, just fitting different use cases. +:::note +A note on navigation with relative URLs: Currently, to support multiple navigation stacks, relative URLs are something not supported +::: + ## Lazy loading routes Now the current way our routes are setup makes it so they are included in the same chunk as the root app.module, which is not ideal. Instead, the router has a setup that allows the components to be isolated to their own chunks. From db9d346966a8e3a4781904fab233e614db4eef3b Mon Sep 17 00:00:00 2001 From: Sean Perkins Date: Tue, 30 May 2023 14:43:35 -0400 Subject: [PATCH 3/4] docs(angular): relative routing is supported Co-authored-by: rdlabo> --- versioned_docs/version-v6/angular/navigation.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/versioned_docs/version-v6/angular/navigation.md b/versioned_docs/version-v6/angular/navigation.md index fd50cc3e29c..9ac7059bde0 100644 --- a/versioned_docs/version-v6/angular/navigation.md +++ b/versioned_docs/version-v6/angular/navigation.md @@ -118,10 +118,6 @@ export class LoginComponent { Both options provide the same navigation mechanism, just fitting different use cases. -:::note -A note on navigation with relative URLs: Currently, to support multiple navigation stacks, relative URLs are something not supported -::: - ### Navigating using LocationStrategy.historyGo Angular Router has a [LocationStrategy.historyGo](https://angular.io/api/common/LocationStrategy#historyGo) method that allows developers to move forward or backward through the application history. Let's take a look at an example. From efa2a5feb71cdfac27836f3439fe5bccd5d2cf66 Mon Sep 17 00:00:00 2001 From: Sean Perkins Date: Tue, 30 May 2023 15:16:13 -0400 Subject: [PATCH 4/4] chore: remove note from all doc versions --- docs/angular/navigation.md | 4 ---- versioned_docs/version-v5/angular/navigation.md | 4 ---- 2 files changed, 8 deletions(-) diff --git a/docs/angular/navigation.md b/docs/angular/navigation.md index eb05502309c..9ad675058a0 100644 --- a/docs/angular/navigation.md +++ b/docs/angular/navigation.md @@ -118,10 +118,6 @@ export class LoginComponent { Both options provide the same navigation mechanism, just fitting different use cases. -:::note -A note on navigation with relative URLs: Currently, to support multiple navigation stacks, relative URLs are something not supported -::: - ### Navigating using LocationStrategy.historyGo Angular Router has a [LocationStrategy.historyGo](https://angular.io/api/common/LocationStrategy#historyGo) method that allows developers to move forward or backward through the application history. Let's take a look at an example. diff --git a/versioned_docs/version-v5/angular/navigation.md b/versioned_docs/version-v5/angular/navigation.md index 0e5148442b8..9dcbcc88949 100644 --- a/versioned_docs/version-v5/angular/navigation.md +++ b/versioned_docs/version-v5/angular/navigation.md @@ -109,10 +109,6 @@ export class LoginComponent { Both options provide the same navigation mechanism, just fitting different use cases. -:::note -A note on navigation with relative URLs: Currently, to support multiple navigation stacks, relative URLs are something not supported -::: - ## Lazy loading routes Now the current way our routes are setup makes it so they are included in the same chunk as the root app.module, which is not ideal. Instead, the router has a setup that allows the components to be isolated to their own chunks.