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.

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

docs(material/chips): use correct terminology #24798

Merged
merged 1 commit into from
Apr 19, 2022
Merged

docs(material/chips): use correct terminology #24798

merged 1 commit into from
Apr 19, 2022

Conversation

crisbeto
Copy link
Member

Fixes that we were referring to MatChip as a component even though it's a directive.

Fixes #24779.

@crisbeto
docs(material/chips): use correct terminology
d8a9d9f 
Fixes that we were referring to `MatChip` as a component even though it's a directive.

Fixes angular#24779.
@crisbeto crisbeto added docs This issue is related to documentation merge safe P4 A relatively minor issue that is not relevant to core functions target: patch This PR is targeted for the next patch release labels Apr 19, 2022
@crisbeto crisbeto requested a review from devversion April 19, 2022 09:01
@crisbeto crisbeto requested a review from andrewseguin as a code owner April 19, 2022 09:01
@crisbeto crisbeto added the action: merge The PR is ready for merge by the caretaker label Apr 19, 2022
@zarend zarend merged commit cb2f493 into angular:master Apr 19, 2022
zarend pushed a commit that referenced this pull request Apr 19, 2022
@crisbeto @zarend
docs(material/chips): use correct terminology (#24798)
ab04f21 
Fixes that we were referring to `MatChip` as a component even though it's a directive.

Fixes #24779.

(cherry picked from commit cb2f493)
@sync-by-unito sync-by-unito bot mentioned this pull request Apr 22, 2022
Closed
@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 20, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Reviewers

@devversion devversion devversion approved these changes

@andrewseguin andrewseguin Awaiting requested review from andrewseguin

Assignees
No one assigned
Labels
action: merge The PR is ready for merge by the caretaker docs This issue is related to documentation P4 A relatively minor issue that is not relevant to core functions target: patch This PR is targeted for the next patch release
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

docs-bug(mat-chip): MatChip is stated to be a Component but is really a Directive
3 participants
@crisbeto @devversion @zarend