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(material/menu): remove dependency on NgClass #28877

Merged
merged 1 commit into from Apr 15, 2024

Conversation

crisbeto
Copy link
Member

We can set classes directly through [class] instead of having to import NgClass. I had to adjust the code a bit, because the built-in [class] binding doesn't do diffing on the object literal.

We can set classes directly through `[class]` instead of having to import `NgClass`. I had to adjust the code a bit, because the built-in `[class]` binding doesn't do diffing on the object literal.
@crisbeto crisbeto added the target: patch This PR is targeted for the next patch release label Apr 13, 2024
@Sergiobop
Copy link

hi @crisbeto , why are you doing these PRs removing ngClass?

It's a bad practice to use it? Should we always use [class] instead?
Thanks

@crisbeto
Copy link
Member Author

I wouldn't say it's a bad practice, I'm just cleaning up the places where we can get away with the simpler binding and to reduce the number of dependencies.

@crisbeto crisbeto added the action: merge The PR is ready for merge by the caretaker label Apr 15, 2024
@crisbeto crisbeto merged commit 9381f90 into angular:main Apr 15, 2024
24 of 27 checks passed
crisbeto added a commit that referenced this pull request Apr 15, 2024
We can set classes directly through `[class]` instead of having to import `NgClass`. I had to adjust the code a bit, because the built-in `[class]` binding doesn't do diffing on the object literal.

(cherry picked from commit 9381f90)
@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 May 16, 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: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants