Title: Signal Forms: enhance validation interop with `ngModel` / reactive forms · Issue #69756 · angular/angular · GitHub
Open Graph Title: Signal Forms: enhance validation interop with `ngModel` / reactive forms · Issue #69756 · angular/angular
X Title: Signal Forms: enhance validation interop with `ngModel` / reactive forms · Issue #69756 · angular/angular
Description: Which @angular/* package(s) are relevant/related to the feature request? forms Description I saw #65769 but I think this case is different: As library developer, I was trying to migrate our custom controls to the new FormValueControl. So...
Open Graph Description: Which @angular/* package(s) are relevant/related to the feature request? forms Description I saw #65769 but I think this case is different: As library developer, I was trying to migrate our custom ...
X Description: Which @angular/* package(s) are relevant/related to the feature request? forms Description I saw #65769 but I think this case is different: As library developer, I was trying to migrate our custom ...
Opengraph URL: https://github.com/angular/angular/issues/69756
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Signal Forms: enhance validation interop with `ngModel` / reactive forms","articleBody":"### Which @angular/* package(s) are relevant/related to the feature request?\n\nforms\n\n### Description\n\nI saw #65769 but I think this case is different:\n\nAs library developer, I was trying to migrate our custom controls to the new `FormValueControl`.\nSo a very common scenario will be, that our custom controls implementing `FormValueControl` will be used with `ngModel` / `formControl`. \nWhile this very basic scenario works very well, we usually also have `Validator` implemented on those custom controls.\nWhich no longer works.\n\nTo be very precise, we basically have this setup:\n\n```ts\n/** Library code */\n@Component({selector: `library-form-control`})\nclass MyCustomControl implements FormValueControl\u003cnumber>, Validator {\n ...\n}\n\n/** Client / library consumer code */\n@Component({template: `\u003clibrary-form-control [(ngModel)]=\"value\"})\nclass ClientForm {\n value = 0;\n}\n```\n\n### Proposed solution\n\nI fully understand, that validation should be declared on the form schema. But ONLY in cases where `ngModel` / `formControl` are used it would be very helpful for migration, if `NG_VALIDATORS` would still be picked up by `ngModel` / `formControl` even if `FormControlValue` is used. \n\n### Alternatives considered\n\n`transformedValue` is really nice, but does not help in all cases. We also have non parsing related validation.\n\nWe could just announce this as a breaking change, but it is expected that this has a stronger impact. Especially since this is hard to detect since there are not type errors.\n\nJust staying on `ControlValueAccessor` for ever, which obviously works. ","author":{"url":"https://github.com/spike-rabbit","@type":"Person","name":"spike-rabbit"},"datePublished":"2026-07-13T12:57:39Z","url":"https://github.com/angular/angular/issues/69756"}
| 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:dd74492c-57ec-3d8c-8ffc-11bfce363503 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | 97B8:9E08E:3C7852:4C487C:6B01FBFA |
| html-safe-nonce | 4fd0d59fa95e19904ebc99cd22fec5bcc0b5a04627cd4f5b4663eb4ee3960f96 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiI5N0I4OjlFMDhFOjNDNzg1Mjo0QzQ4N0M6NkIwMUZCRkEiLCJ2aXNpdG9yX2lkIjoiNTA2ODM4NDg2MDc2NzM4NjYxOSIsInJlZ2lvbl9lZGdlIjoiaWFkIiwicmVnaW9uX3JlbmRlciI6ImlhZCJ9 |
| visitor-hmac | 12deebeba1ef32f2dcaa69c2c65b797e12c32943d12335391a5c50fadfebbc53 |
| hovercard-subject-tag | issue:4873835567 |
| 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/69756/issue_layout |
| twitter:image | https://opengraph.githubassets.com/cf05215ba744a9c314305609df9b9ccbd710d88e57a898bf06e576d413a21587/angular/angular/issues/69756 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/cf05215ba744a9c314305609df9b9ccbd710d88e57a898bf06e576d413a21587/angular/angular/issues/69756 |
| og:image:alt | Which @angular/* package(s) are relevant/related to the feature request? forms Description I saw #65769 but I think this case is different: As library developer, I was trying to migrate our custom ... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | spike-rabbit |
| 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