Title: signal forms: support ngValue and compareWith for select · Issue #64670 · angular/angular · GitHub
Open Graph Title: signal forms: support ngValue and compareWith for select · Issue #64670 · angular/angular
X Title: signal forms: support ngValue and compareWith for select · Issue #64670 · angular/angular
Description: Which @angular/* package(s) are relevant/related to the feature request? forms (signal) Description Unless I missed something, there doesn't seem to be a way to support binding a non-string value to a
Open Graph Description: Which @angular/* package(s) are relevant/related to the feature request? forms (signal) Description Unless I missed something, there doesn't seem to be a way to support binding a non-string value t...
X Description: Which @angular/* package(s) are relevant/related to the feature request? forms (signal) Description Unless I missed something, there doesn't seem to be a way to support binding a non-string val...
Opengraph URL: https://github.com/angular/angular/issues/64670
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"signal forms: support ngValue and compareWith for select","articleBody":"### Which @angular/* package(s) are relevant/related to the feature request?\n\nforms (signal)\n\n### Description\n\nUnless I missed something, there doesn't seem to be a way to support binding a non-string value to a `\u003cselect>` element in signals form.\n\n\n\n### Proposed solution\n\nIt would be hugely useful if signal forms supported the same functionality as reactive forms regarding selects, namely `ngValue` on `\u003coption>` elements, allowing to bind the option to any kind of value (typically objects with some identifier), and `compareWith` on `\u003cselect>` elements, allowing to specify that these objects must be compared to the current value of the control using a provided equality function.\n\n### Alternatives considered\n\nLeave it as is, and force developers to bind to the identifier of the object, and have some computed signal outside of the form model that finds the object with the selected identifier inside the list of options, but that is not ideal IMHO. ","author":{"url":"https://github.com/jnizet","@type":"Person","name":"jnizet"},"datePublished":"2025-10-25T10:15:19Z","url":"https://github.com/angular/angular/issues/64670"}
| 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:09f803d2-5779-b3a5-5209-e7355208fa59 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | C232:BB75:F0F4D6:13FBE99:6B01DA25 |
| html-safe-nonce | 8505bc5a20b4c318afdae4e26dc23d22f1e6922ae81b3ef8f6d711e8de3bab83 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJDMjMyOkJCNzU6RjBGNEQ2OjEzRkJFOTk6NkIwMURBMjUiLCJ2aXNpdG9yX2lkIjoiNjA1MDg4ODA3MTcyODE5MjAzNyIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | ff6458cb52eeeb146e6a2cfc32602e5950f2d6dd0b21b7d0e55ef68d50c86b0f |
| hovercard-subject-tag | issue:3552286307 |
| 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/64670/issue_layout |
| twitter:image | https://opengraph.githubassets.com/13cd71cfb885ba8a6165d79ccb4d5e293eff8d109d331c5e54470eadde3ead25/angular/angular/issues/64670 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/13cd71cfb885ba8a6165d79ccb4d5e293eff8d109d331c5e54470eadde3ead25/angular/angular/issues/64670 |
| og:image:alt | Which @angular/* package(s) are relevant/related to the feature request? forms (signal) Description Unless I missed something, there doesn't seem to be a way to support binding a non-string value t... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | jnizet |
| hostname | github.com |
| expected-hostname | github.com |
| None | cc5dfdd32f62ebd3223cab3af3aa2b268d3605218237326a48a99d1efd89495c |
| 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 | 8c77c9e8439031ad54c75a250694842892f693e1 |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width