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(multiple): remove workarounds for formControl directive #29296

Merged
merged 1 commit into from
Jun 25, 2024

Conversation

mmalerba
Copy link
Contributor

blocked on #29295

@mmalerba mmalerba added blocked This issue is blocked by some external factor, such as a prerequisite PR target: minor This PR is targeted for the next minor release labels Jun 21, 2024
@angular-robot angular-robot bot added the area: build & ci Related the build and CI infrastructure of the project label Jun 21, 2024
@mmalerba mmalerba removed the blocked This issue is blocked by some external factor, such as a prerequisite PR label Jun 24, 2024
@mmalerba mmalerba marked this pull request as ready for review June 24, 2024 15:36
@mmalerba mmalerba requested a review from a team as a code owner June 24, 2024 15:36
@mmalerba mmalerba requested review from crisbeto and amysorto and removed request for a team June 24, 2024 15:36
@angular-robot angular-robot bot removed the area: build & ci Related the build and CI infrastructure of the project label Jun 24, 2024
@mmalerba mmalerba added the action: merge The PR is ready for merge by the caretaker label Jun 24, 2024
The formControl directive previously did not mark itself for check, so
several components that work closely with this directive marked for
check on its behalf as a workaround. Now that the directive is fixed we
can remove the workarounds.
@mmalerba mmalerba removed the request for review from amysorto June 25, 2024 03:48
@mmalerba mmalerba merged commit aa17c2d into angular:main Jun 25, 2024
22 checks passed
DBowen33 pushed a commit to DBowen33/components that referenced this pull request Jul 3, 2024
…29296)

The formControl directive previously did not mark itself for check, so
several components that work closely with this directive marked for
check on its behalf as a workaround. Now that the directive is fixed we
can remove the workarounds.
@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 Jul 26, 2024
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 target: minor This PR is targeted for the next minor release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants