Skip to content

docs(angular): relative routing is supported #2980

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
May 31, 2023
Merged

docs(angular): relative routing is supported #2980

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
cce9f73
chore: prettier formatting
sean-perkins May 30, 2023
40f53c2
chore: revert invalid changes
sean-perkins May 30, 2023
db9d346
docs(angular): relative routing is supported
sean-perkins May 30, 2023
efa2a5f
chore: remove note from all doc versions
sean-perkins May 30, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 0 additions & 4 deletions docs/angular/navigation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
4 changes: 0 additions & 4 deletions versioned_docs/version-v5/angular/navigation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
4 changes: 0 additions & 4 deletions versioned_docs/version-v6/angular/navigation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down