Title: Rearchitect Router so it's more modular · Issue #42953 · angular/angular · GitHub
Open Graph Title: Rearchitect Router so it's more modular · Issue #42953 · angular/angular
X Title: Rearchitect Router so it's more modular · Issue #42953 · angular/angular
Description: Which @angular/* package(s) are relevant/releated to the feature request? router Description The Angular router's current architecture is problematic for a couple big reasons: It is not extensible. Developers cannot easily extend or chan...
Open Graph Description: Which @angular/* package(s) are relevant/releated to the feature request? router Description The Angular router's current architecture is problematic for a couple big reasons: It is not extensible....
X Description: Which @angular/* package(s) are relevant/releated to the feature request? router Description The Angular router's current architecture is problematic for a couple big reasons: It is not extensi...
Opengraph URL: https://github.com/angular/angular/issues/42953
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Rearchitect Router so it's more modular","articleBody":"### Which @angular/* package(s) are relevant/releated to the feature request?\r\n\r\nrouter\r\n\r\n### Description\r\n\r\nThe Angular router's current architecture is problematic for a couple big reasons:\r\n\r\n* It is not extensible. Developers cannot easily extend or change the Router's functionality to support features that would be useful to their applications. Instead, these features have to be built in to the core Router code and exposed through some endpoint (i.e. `RouteReuseStrategy`, some option on `ExtraOptions` which is used as an switch in the internal code, etc.)\r\n* It is not tree shakeable. Due to its non-modular nature, almost all features (lazy loading, guards, resolvers) are generally baked in to the Router's internals unless explicitly configurable through a `Strategy` that can provide a `no-op` implementation. Simple applications that do not use these features still incur the bundle size cost.\r\n\r\n\r\n### Proposed solution\r\n\r\nBecause of the above two problems, we're often quite limited on what features we can implement. The router should be rearchitected with the following goals in mind:\r\n\r\n* Tree-shakeability\r\n* More configurable features, such as\r\n * #24187\r\n * #40577\r\n * #10556 / #24956\r\n * #16416\r\n * Configurable browser history management, for example\r\n * Ability to use the upcoming [App History API](https://github.com/WICG/app-history)\r\n * #42915\r\n * Ability to fix issues like #13586 without having to wait for the baked-in fix\r\n* General ability to use @angular/router to build custom routing solutions, which will likely require exposing more of the router internals such as:\r\n * #38951\r\n * #25630 / #24069\r\n\r\n### Alternatives considered\r\n\r\nN/A","author":{"url":"https://github.com/atscott","@type":"Person","name":"atscott"},"datePublished":"2021-07-23T22:09:26Z","url":"https://github.com/angular/angular/issues/42953"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322 |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:474abcd4-9f5b-8ef9-c408-dc5b74ec7f17 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | C0B0:3D97C8:979A94:CC222B:6B00E8A4 |
| html-safe-nonce | 519a3bd48b7cd40e9e59a8a6713bf0480b91ee857e1a6366c86cdff265e711b1 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJDMEIwOjNEOTdDODo5NzlBOTQ6Q0MyMjJCOjZCMDBFOEE0IiwidmlzaXRvcl9pZCI6Ijg0MzU3OTU3OTM4NjQwOTE4MTIiLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ== |
| visitor-hmac | 9571c8b31995b2a49ac234eff9814723ad08c42f0e265756bd5679eb61d2d08c |
| hovercard-subject-tag | issue:951925032 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/angular/angular/42953/issue_layout |
| twitter:image | https://opengraph.githubassets.com/e6689ef9af638d43951530fa9870e24b56e96a29402da8e334ffe82e91ec7cb9/angular/angular/issues/42953 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/e6689ef9af638d43951530fa9870e24b56e96a29402da8e334ffe82e91ec7cb9/angular/angular/issues/42953 |
| og:image:alt | Which @angular/* package(s) are relevant/releated to the feature request? router Description The Angular router's current architecture is problematic for a couple big reasons: It is not extensible.... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | atscott |
| hostname | github.com |
| expected-hostname | github.com |
| None | 27088b6977484d0d3321d9a11c907c6d6637b315cfa359ef7952dbf6292f9b14 |
| turbo-cache-control | no-preview |
| go-import | github.com/angular/angular git https://github.com/angular/angular.git |
| octolytics-dimension-user_id | 139426 |
| octolytics-dimension-user_login | angular |
| octolytics-dimension-repository_id | 24195339 |
| octolytics-dimension-repository_nwo | angular/angular |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 24195339 |
| octolytics-dimension-repository_network_root_nwo | angular/angular |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 624179fb8b88d26ba5bba08894eb60a1c5a1d93d |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width