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

Remove error mixin usages #28149

Merged
merged 5 commits into from
Nov 20, 2023
Merged

Remove error mixin usages #28149

merged 5 commits into from
Nov 20, 2023

Conversation

crisbeto
Copy link
Member

Removes all remaining usages of the error mixin by moving the functionality into a new class that is used internally inside the components. This allows us to further clean up some boilerplate and a hacky workaround in the chip grid.

@crisbeto crisbeto added P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent target: patch This PR is targeted for the next patch release merge: preserve commits When the PR is merged, a rebase and merge should be performed labels Nov 18, 2023
@crisbeto crisbeto force-pushed the error-mixin-removal branch 3 times, most recently from 505aca2 to b562169 Compare November 19, 2023 07:51
Moves the error tracking behavior into a separate class that we can use instead of `mixinErrorState`.
Replaces the final TypeScript mixin used by `MatInput` with an internal class.
Replaces the final TypeScript mixin used by `MatSelect` with an internal class.
Replaces the final TypeScript mixin used by `MatChipGrid` with an internal class.
Replaces the final TypeScript mixin used by `MatStartDate` and `MatEndDate` with an internal class.
@crisbeto crisbeto added target: minor This PR is targeted for the next minor release and removed target: patch This PR is targeted for the next patch release labels Nov 20, 2023
@crisbeto crisbeto added the action: merge The PR is ready for merge by the caretaker label Nov 20, 2023
@crisbeto crisbeto merged commit 576f44f into angular:main Nov 20, 2023
28 checks passed
crisbeto added a commit to crisbeto/material2 that referenced this pull request Nov 24, 2023
The changes from angular#28149 appear to have triggered an error when `mat-chip-grid` is used inside of a `mat-form-field` and optimized with Closure compiler in a configuration that uses type information to do property renaming. These changes work around the issue within `mat-form-field`.
crisbeto added a commit that referenced this pull request Nov 24, 2023
The changes from #28149 appear to have triggered an error when `mat-chip-grid` is used inside of a `mat-form-field` and optimized with Closure compiler in a configuration that uses type information to do property renaming. These changes work around the issue within `mat-form-field`.
@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 Dec 21, 2023
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 merge: preserve commits When the PR is merged, a rebase and merge should be performed P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent target: minor This PR is targeted for the next minor release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants