Skip to content

Conversation

@crisbeto
Copy link
Member

Fixes that the valueChanges stream from reactive forms was emitting on init for the timepicker input. It was because we had an effect that was meant to trigger min/max revalidation.

I also ended up consolidating all the validation updates into a single effect so we don't have multiple sources of changes.

Fixes #32423.

Fixes that the `valueChanges` stream from reactive forms was emitting on init for the timepicker input. It was because we had an `effect` that was meant to trigger `min`/`max` revalidation.

I also ended up consolidating all the validation updates into a single effect so we don't have multiple sources of changes.

Fixes angular#32423.
@crisbeto crisbeto added the target: patch This PR is targeted for the next patch release label Nov 28, 2025
@crisbeto crisbeto requested a review from a team as a code owner November 28, 2025 06:46
@crisbeto crisbeto requested review from mmalerba and ok7sai and removed request for a team November 28, 2025 06:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: material/timepicker target: patch This PR is targeted for the next patch release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bug(Timepicker): valueChanges-event is called during initialization

1 participant