Skip to content

Conversation

@lekhmanrus
Copy link
Contributor

  • Prevent the timepicker min/max validator effect from triggering form control value changes during initial setup.
  • Add appropriate unit test

close #32423

@lekhmanrus lekhmanrus requested a review from a team as a code owner November 27, 2025 21:25
@lekhmanrus lekhmanrus requested review from adolgachev and crisbeto and removed request for a team November 27, 2025 21:25
@crisbeto
Copy link
Member

It's not as concise, but I think the right approach is #32434 so that we don't have multiple effects trying to update the value.

@crisbeto crisbeto closed this Dec 1, 2025
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Jan 1, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

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

2 participants