Title: Introduce custom/proxy signals for fine-grained read/write control · Issue #68280 · angular/angular · GitHub
Open Graph Title: Introduce custom/proxy signals for fine-grained read/write control · Issue #68280 · angular/angular
X Title: Introduce custom/proxy signals for fine-grained read/write control · Issue #68280 · angular/angular
Description: Which @angular/* package(s) are relevant/related to the feature request? core Description Currently, Angular provides a robust Signal API, but lacks a primitive to explicitly intercept and control both the get (dependency tracking) and s...
Open Graph Description: Which @angular/* package(s) are relevant/related to the feature request? core Description Currently, Angular provides a robust Signal API, but lacks a primitive to explicitly intercept and control ...
X Description: Which @angular/* package(s) are relevant/related to the feature request? core Description Currently, Angular provides a robust Signal API, but lacks a primitive to explicitly intercept and control ...
Opengraph URL: https://github.com/angular/angular/issues/68280
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Introduce custom/proxy signals for fine-grained read/write control","articleBody":"### Which @angular/* package(s) are relevant/related to the feature request?\n\ncore\n\n### Description\n\nCurrently, Angular provides a robust Signal API, but lacks a primitive to explicitly intercept and control both the `get` (dependency tracking) and `set` (update triggering) operations of a WritableSignal while preserving its standard interface.\n\nThis makes it difficult to model transactional updates between reactive state and external APIs (Storage, DOM, timers etc.). Relying on `effect` for synchronization is often insufficient because its asynchronous, coalescing nature cannot guarantee atomic consistency between state and external side effects.\n\n### Proposed solution\n\nIntroduce a new primitive, such as `customSignal` or `proxySignal`, that allows developers to wrap an existing signal or define a new one with intercepted `get` and `set` handlers.\n\n### Examples (pseudocode)\n\n#### Persistent signal (external side effects):\n\n```ts\nfunction storageSignal\u003cT>(key: string, initialValue: T): WritableSignal\u003cT> {\n const source = signal\u003cT>(initialValue);\n\n return proxySignal(source, {\n set: (value, node) => {\n /**\n * Ensures a synchronous transaction in which state and storage are updated atomically.\n * This guarantees deterministic side effects, including immediate cross-tab `storage` event dispatch,\n * and avoids scheduling delays and value coalescing inherent to `effect()`.\n */\n localStorage.setItem(key, JSON.stringify(value));\n node.set(value);\n }\n });\n}\n```\nAdditionally, this approach allows us to ensure consistency between the signal state and external side effects:\n```ts\ntry {\n // localStorage can throw QuotaExceededError\n localStorage.setItem(key, JSON.stringify(value));\n // the signal is updated only if the write operation succeeds.\n node.set(value);\n} catch {\n /* ... */\n}\n```\n#### Throttled signal (custom update scheduling):\n\n```ts\nfunction throttledSignal\u003cT>(initialValue: T, delay = 200) {\n let lastEmit = 0;\n\n const source = signal(initialValue);\n\n return proxySignal(source, {\n set: (value, node) => {\n const wait = delay - (Date.now() - lastEmit);\n const emit = () => { lastEmit = Date.now(); node.set(value); };\n // Custom update scheduler:\n wait \u003c= 0 ? emit() : setTimeout(emit, wait);\n }\n });\n}\n```\n\n#### Fallback signal:\n```ts\nfunction routeQuerySignal\u003cT>(\n key: string,\n defaultValue?: T\n) {\n const source = signal\u003cT | undefined>(undefined);\n\n return proxySignal(source, {\n get: (node) => {\n const value = node();\n return value !== undefined ? value : defaultValue;\n },\n });\n}\n```\n\n### Design considerations\n- While `get` interception enables control over dependency tracking, there are almost no compelling real-world use cases requiring such fine-grained control. It is primarily included for API symmetry and typically delegates directly to the underlying tracking mechanism. However, inspired by patterns such as Vue’s `customRef`, some libraries use it to either transform values or provide fallback values during read operations.\n\n- At this stage, the proposal focuses on the conceptual idea with illustrative examples, without defining a concrete API shape. The goal is to discuss the potential of this primitive with the community and contributors, and better understand its demand. In most cases, such functionality is primarily relevant for libraries built on top of signals.\n\n### Alternatives considered\n\n- Using `effect()`, which is asynchronous. It cannot intercept or modify the value before it is written to the signal. Additionally, we sometimes have to create a consumer that unnecessarily shows up in the dev tools.\n- Creating custom wrapper objects/classes (e.g., `{ value: Signal, set: (v) => void }`), which breaks the WritableSignal API signature.\n- Building custom primitives to manually proxy read/write.","author":{"url":"https://github.com/vs-borodin","@type":"Person","name":"vs-borodin"},"datePublished":"2026-04-19T18:31:11Z","url":"https://github.com/angular/angular/issues/68280"}
| 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:d66b2a8e-f4d1-4daa-81fe-ff7b59e5fcbc |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | B552:785A9:43C4D15:55E8CA8:6B022DB7 |
| html-safe-nonce | 98b9fa2906f3cd9477e0866c839609e7d813dd0cbd35e6b96df51bf8ae45e8b0 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJCNTUyOjc4NUE5OjQzQzREMTU6NTVFOENBODo2QjAyMkRCNyIsInZpc2l0b3JfaWQiOiI0ODgxNTIzMjkzNDE4NTY1MDQ3IiwicmVnaW9uX2VkZ2UiOiJpYWQiLCJyZWdpb25fcmVuZGVyIjoiaWFkIn0= |
| visitor-hmac | 8593e16aa69e839eb687a2ff0a15e850638977709ff6d02e93e7658de78e0658 |
| hovercard-subject-tag | issue:4291662013 |
| 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/68280/issue_layout |
| twitter:image | https://opengraph.githubassets.com/6f0b83ec2389433785510ce0e811b09238e62e0b86f50375e2d140ea2ae08758/angular/angular/issues/68280 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/6f0b83ec2389433785510ce0e811b09238e62e0b86f50375e2d140ea2ae08758/angular/angular/issues/68280 |
| og:image:alt | Which @angular/* package(s) are relevant/related to the feature request? core Description Currently, Angular provides a robust Signal API, but lacks a primitive to explicitly intercept and control ... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | vs-borodin |
| hostname | github.com |
| expected-hostname | github.com |
| None | 87e774ee7c6b3bee0490394e4d3e57ec9dbc956f74b87ea685dc8996c1676456 |
| 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 | 423dbb54c5e7bfecc838eb387c1435eb3d0e760d |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width