Skip to content

Review pass & fixup of the control directive & related code #63068

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 18 commits into from
Aug 19, 2025

Conversation

mmalerba
Copy link
Contributor

@mmalerba mmalerba commented Aug 9, 2025

No description provided.

@mmalerba mmalerba requested review from leonsenft and kirjs August 9, 2025 09:18
@mmalerba mmalerba added area: forms target: feature This PR is targeted for a feature branch (outside of main and semver branches) labels Aug 9, 2025
@ngbot ngbot bot added this to the Backlog milestone Aug 9, 2025
@angular-robot angular-robot bot added detected: feature PR contains a feature commit area: docs Related to the documentation labels Aug 9, 2025
Copy link
Contributor Author

@mmalerba mmalerba left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Calling out some TODOs in case we want to address any of them during this PR

@mmalerba mmalerba requested review from alxhub and removed request for JeanMeche and AndrewKushnir August 9, 2025 09:25
@pullapprove pullapprove bot requested a review from JeanMeche August 9, 2025 09:25
@mmalerba mmalerba changed the title feat(forms): add missing builtin property hooks for custom controls Review pass & fixup of the control directive & related code Aug 9, 2025
Copy link
Contributor

@leonsenft leonsenft left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't really have answers for a lot of the questions/TODOs. Would it make sense adding them to the backlog and linking the TODOs to those issues–or did you mean to address them all before landing this?

@mmalerba
Copy link
Contributor Author

re: TODOs - hoping Alex will have a chance to comment on some of them, if not I'll leave them in an add an item to our backlog

@mmalerba mmalerba requested a review from leonsenft August 19, 2025 21:57
Comment on lines +15 to +17
// TODO: `ValidationError` and `DisabledReason` are inherently tied to the signal forms system.
// They don't make sense when using a ccontrol separately from the forms system and setting the
// inputs individually. Givn that, should they still be part of this interface?
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When in doubt, keep the API smaller? If they don't make sense maybe we leave it out unless there's a clear use case or requirement for them?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm pretty sure we will want them in some form, but we may want to make the types more friendly to standalone use. I'll address the TODO in a followup after Alex has a chance to chime in

@mmalerba mmalerba merged commit 9866f91 into angular:prototype/signal-forms Aug 19, 2025
13 of 16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: docs Related to the documentation area: forms detected: feature PR contains a feature commit target: feature This PR is targeted for a feature branch (outside of main and semver branches)
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

3 participants