Title: devtools(signal graph): internal framework signals can overwhelm application signals · Issue #65894 · angular/angular · GitHub
Open Graph Title: devtools(signal graph): internal framework signals can overwhelm application signals · Issue #65894 · angular/angular
X Title: devtools(signal graph): internal framework signals can overwhelm application signals · Issue #65894 · angular/angular
Description: Is this a bug report or a feature request? Bug Report Feature Request Description [Feature Request only] Request: some way to filter out internal framework signals from the devtools signal graph Explanation + Concerns A recent draft PR h...
Open Graph Description: Is this a bug report or a feature request? Bug Report Feature Request Description [Feature Request only] Request: some way to filter out internal framework signals from the devtools signal graph Ex...
X Description: Is this a bug report or a feature request? Bug Report Feature Request Description [Feature Request only] Request: some way to filter out internal framework signals from the devtools signal graph Ex...
Opengraph URL: https://github.com/angular/angular/issues/65894
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"devtools(signal graph): internal framework signals can overwhelm application signals","articleBody":"### Is this a bug report or a feature request?\n\n- [ ] Bug Report\n- [x] Feature Request\n\n### Description [Feature Request only]\n\n# Request: some way to filter out internal framework signals from the devtools signal graph\n\n## Explanation + Concerns\n\nA recent draft PR has surfaced an enhancement to the signal graph that has been on my mind\n\n[refactor(router): Update RouterLinkActive to use signals #65892](https://github.com/angular/angular/pull/65892#issuecomment-3618988813)\n\nMy take I was told to spin into this issue: \n\nThis is probably a larger question(s) beyond the scope of this, but this change reminds me of something I have been intending to make an issue about and this may inform/save that.\n\nQuestion: Do these internal signals show up in the devtools? If so, would it be possible to opt them out with existing framework functionality?\n\nOne thing about reactive forms adopting signals internally is that the signal graph in the devtools has so much noise from internal signal state. This internal change was made before the signal devtools, but I was curious if something like this would inherit showing all those internal properties. To be honest the noise in reactive forms in particular makes it hard to see application signals, and upon seeing this PR I have some concern if this will add more noise.\n\nFor example, check out this reproduction: https://stackblitz.com/edit/stackblitz-starters-1mfuv5ek?file=src%2Fmain.ts\n\n## Example: one user signal vs different basic reactive form signal internals\n\n```ts\n// Reproduction also includes a form group with a control and the relatively new form array with a control\n// Can comment out individually to isolate + scale\n@Component({\n template: `\n \u003cp>{{applicationSignal()}}\u003c/p>\n\n \u003cinput [formControl]=\"reactiveFormControl\" />\n `,\n imports: [ReactiveFormsModule],\n})\nexport class App {\n applicationSignal = signal('application signal value');\n\n reactiveFormControl = new FormControl('form control value');\n}\n```\n\n\u003cimg width=\"205\" height=\"196\" alt=\"Signal graph of one application signal and 6 internal form signals\" src=\"https://github.com/user-attachments/assets/3a2cee24-713e-4f73-b5bb-5fca52c2baaa\" />\n\nAs you can see, the one user written signal is a fraction of the six internal framework signals used for a form control.\n\n| Form class type | Internal signals |\n| --- | --- |\n| 1 `FormControl` (FC) | 6 |\n| 1 `FormGroup` with 1 FC | 14 |\n| 1 `FormArray` with 1 FC | 14 | \n\nAll versus a single user written signal. I do reactive forms all day and even a single control or small group could out-scale most signals I write myself in a component.\n\nMy concern is that as more signals are used internally, that it becomes harder to see my application's signals. It is already an issue IMO with reactive forms.\n\n### Proposed solution [Feature Request only]\n\nFour options I think could all have advantages\n\n- Existing convention: Be able to filter out framework signals, akin to \"Hide Framework Injectors\" in the Injector Tree\n- Most out of sight of user: Perhaps just not even show them? This usage of signals internally in forms predates the signal devtools, but I mention this now since it looks like more signals will be used internally in existing APIs. \n- Distinction: Place internal signals in a different cluster than application signals, or with different shapes/colors. Tbh to me this sounds reaching and plausibly just as confusing, but it came to mind.\n- Potentially radical: [\"Compound signals\" visualization](https://github.com/angular/angular/issues/63227). Like how the resource visualizer PR linked in that issue is like. I do think it could be cool and useful to see internal signals, but I imagine that could be confusing and a lot of work. But I thought at least for reactive forms that it would be cool to see values in the tree in a condensed way, though I know that API in particular has nuances in those values that may not be applicable/accurate timing for users.\n\n### Alternatives considered [Feature Request only]\n\nUse other parts of the devtooling or continue panning around to find my authored signals. To be honest, almost all apps I make even with relatively low amount of form classes can make it really hard to find my own values.","author":{"url":"https://github.com/michael-small","@type":"Person","name":"michael-small"},"datePublished":"2025-12-06T00:54:06Z","url":"https://github.com/angular/angular/issues/65894"}
| 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:925ae9b2-f5c9-a460-83ab-4125e3ca0003 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | E660:26DC6B:313CBD:4373FB:6AFDDF70 |
| html-safe-nonce | a2566a35fb7278c6f792ff89614d5b9a6eeac7aa210de028b9509b96557f0054 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJFNjYwOjI2REM2QjozMTNDQkQ6NDM3M0ZCOjZBRkRERjcwIiwidmlzaXRvcl9pZCI6IjI4MjMzNDA5MzYxNDkxOTY2NTYiLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ== |
| visitor-hmac | 9c8633d6301b5917211ee3cf2ac91a99b7067200e45c889dda38513fb748d401 |
| hovercard-subject-tag | issue:3700736603 |
| 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/65894/issue_layout |
| twitter:image | https://opengraph.githubassets.com/fa192e6361ed11dcaed75785184310ac07673ff9b6efae17069f042b0f0cb9ad/angular/angular/issues/65894 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/fa192e6361ed11dcaed75785184310ac07673ff9b6efae17069f042b0f0cb9ad/angular/angular/issues/65894 |
| og:image:alt | Is this a bug report or a feature request? Bug Report Feature Request Description [Feature Request only] Request: some way to filter out internal framework signals from the devtools signal graph Ex... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | michael-small |
| hostname | github.com |
| expected-hostname | github.com |
| None | 90d7884679efe0f89b35e0eef84213a75179f38d11a62f2a0af551bbe5110799 |
| 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 | 89e3d4b2f59ef440fc496c853aee1d9a06a137d6 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width