Skip to content
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

fix(cdk/listbox): incorrectly validating preselected value #25893

Merged

Conversation

crisbeto
Copy link
Member

In #25856 the check that verifies the validity of the form control value was moved into writeValue. This works as expected for assignments after initialization, but it throws an error incorrectly if there is a preselected value, because writeValue will be called before the options are available.

These changes resolve the issue by checking that the options have been initialized before throwing the error.

@crisbeto crisbeto added P2 The issue is important to a large percentage of users, with a workaround target: rc This PR is targeted for the next release-candidate labels Oct 29, 2022
In angular#25856 the check that verifies the validity of the form control value was moved into `writeValue`. This works as expected for assignments after initialization, but it throws an error incorrectly if there is a preselected value, because `writeValue` will be called before the options are available.

These changes resolve the issue by checking that the options have been initialized before throwing the error.
@crisbeto crisbeto force-pushed the cdk-listbox-preselected-option-validation branch from 4c59a65 to bf7194f Compare October 29, 2022 07:10
@crisbeto crisbeto self-assigned this Oct 29, 2022
@crisbeto crisbeto added the action: merge The PR is ready for merge by the caretaker label Oct 29, 2022
@crisbeto crisbeto merged commit 166ed5e into angular:main Oct 29, 2022
crisbeto added a commit that referenced this pull request Oct 29, 2022
In #25856 the check that verifies the validity of the form control value was moved into `writeValue`. This works as expected for assignments after initialization, but it throws an error incorrectly if there is a preselected value, because `writeValue` will be called before the options are available.

These changes resolve the issue by checking that the options have been initialized before throwing the error.

(cherry picked from commit 166ed5e)
@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 Nov 29, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker P2 The issue is important to a large percentage of users, with a workaround target: rc This PR is targeted for the next release-candidate
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants