Skip to content

fix(material/timepicker): prevent min/max validator effect on init #32425

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.

Sign up for GitHub

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

Jump to bottom
Closed
wants to merge 1 commit into from
Closed

fix(material/timepicker): prevent min/max validator effect on init #32425

wants to merge 1 commit into from

Conversation

@lekhmanrus
Copy link
Contributor

@lekhmanrus lekhmanrus commented Nov 27, 2025

  • 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

crisbeto commented Nov 28, 2025

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@adolgachev adolgachev Awaiting requested review from adolgachev adolgachev is a code owner automatically assigned from angular/components-googlers

@crisbeto crisbeto Awaiting requested review from crisbeto crisbeto is a code owner automatically assigned from angular/components-googlers

Assignees

No one assigned

Labels

area: material/timepicker

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

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

2 participants

@lekhmanrus @crisbeto