Title: feature(router): Provide a way to coalesce multiple failed guards so only a single redirect is called · Issue #24618 · angular/angular · GitHub
Open Graph Title: feature(router): Provide a way to coalesce multiple failed guards so only a single redirect is called · Issue #24618 · angular/angular
X Title: feature(router): Provide a way to coalesce multiple failed guards so only a single redirect is called · Issue #24618 · angular/angular
Description: When there are multiple guards they will run async. If only one of them performs a router.navigateByUrl(url), there shouldn't be a problem. However, sometimes there are multiple guards that will perform a redirect and there isn't a good ...
Open Graph Description: When there are multiple guards they will run async. If only one of them performs a router.navigateByUrl(url), there shouldn't be a problem. However, sometimes there are multiple guards that will pe...
X Description: When there are multiple guards they will run async. If only one of them performs a router.navigateByUrl(url), there shouldn't be a problem. However, sometimes there are multiple guards that wil...
Opengraph URL: https://github.com/angular/angular/issues/24618
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"feature(router): Provide a way to coalesce multiple failed guards so only a single redirect is called","articleBody":"When there are multiple guards they will run async. If only one of them performs a `router.navigateByUrl(url)`, there shouldn't be a problem. However, sometimes there are multiple guards that will perform a redirect and there isn't a good way to determine which is the primary one and which one should run.\r\n\r\nWe need an API that either allows redirects to be scheduled with priority, then \"flushed\" using the highest priority one, or we need to cancel other guards when a guard performs a redirect. Another option would be to collect info from all the guards and let the redirect be configured in a single place.\r\n\r\nThis isn't a very well-defined feature as I think it will take some looking at the current APIs and how the navigation flow works to see what's feasible without introducing wildly breaking changes.","author":{"url":"https://github.com/jasonaden","@type":"Person","name":"jasonaden"},"datePublished":"2018-06-21T21:36:21.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/24618/angular/issues/24618"}
| 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:621aae94-c906-cffa-30b3-85175d3eadf2 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | C390:2E09C7:2438FF:34A384:6A61D8E6 |
| html-safe-nonce | ad3f41b09ed42a4cdfc40bf6cdb8b6d90a0ee26957b3878fe10c37b6c6c0e1c2 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJDMzkwOjJFMDlDNzoyNDM4RkY6MzRBMzg0OjZBNjFEOEU2IiwidmlzaXRvcl9pZCI6Ijc4NDU3NDIyMDAyMDI4NDQzOTAiLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ== |
| visitor-hmac | c78365996643cf905a9f8fa00b0379a0865c96599066bda5a7409e99934ae1e9 |
| hovercard-subject-tag | issue:334666855 |
| 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/24618/issue_layout |
| twitter:image | https://opengraph.githubassets.com/3c7f55b26b22be02953304616e727e009bf37638f5fc04ffe4e4ad89773e0254/angular/angular/issues/24618 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/3c7f55b26b22be02953304616e727e009bf37638f5fc04ffe4e4ad89773e0254/angular/angular/issues/24618 |
| og:image:alt | When there are multiple guards they will run async. If only one of them performs a router.navigateByUrl(url), there shouldn't be a problem. However, sometimes there are multiple guards that will pe... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | jasonaden |
| hostname | github.com |
| expected-hostname | github.com |
| None | b2de8c74e5e61e893155ba46ee41bc66170c1644cb795adefa8386d490f7781c |
| 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 | d1866027ded575df8a15c731dd8b9986c9483ceb |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
Links:
Viewport: width=device-width