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

docs-bug(Chips): No Testing docs for chips harnesses #20507

Closed
mischkl opened this issue Sep 7, 2020 · 1 comment · Fixed by angular/material.angular.io#860
Closed

docs-bug(Chips): No Testing docs for chips harnesses #20507

mischkl opened this issue Sep 7, 2020 · 1 comment · Fixed by angular/material.angular.io#860
Assignees
Labels
area: material.angular.io docs This issue is related to documentation P2 The issue is important to a large percentage of users, with a workaround

Comments

@mischkl
Copy link

mischkl commented Sep 7, 2020

Documentation Feedback

In Angular Material 10.2.0, new testing harnesses were introduced for the chips components, but documentation is missing.

Affected documentation page: https://material.angular.io/components/chips/api

@mischkl mischkl added docs This issue is related to documentation needs triage This issue needs to be triaged by the team labels Sep 7, 2020
@mischkl mischkl changed the title docs-bug(): TITLE docs-bug(Chips): No Testing docs for chips harnesses Sep 7, 2020
@crisbeto crisbeto self-assigned this Sep 7, 2020
@crisbeto crisbeto added area: material.angular.io has pr P2 The issue is important to a large percentage of users, with a workaround and removed needs triage This issue needs to be triaged by the team labels Sep 7, 2020
crisbeto added a commit to crisbeto/material.angular.io that referenced this issue Sep 7, 2020
We've recently added more test harnesses that weren't being reflected in the docs.

Fixes angular/components#20507.
crisbeto added a commit to angular/material.angular.io that referenced this issue Sep 7, 2020
We've recently added more test harnesses that weren't being reflected in the docs.

Fixes angular/components#20507.
@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 Oct 8, 2020
alexeagle pushed a commit to alexeagle/material2 that referenced this issue Nov 6, 2024
We've recently added more test harnesses that weren't being reflected in the docs.

Fixes angular#20507.
alexeagle pushed a commit to alexeagle/material2 that referenced this issue Dec 12, 2024
We've recently added more test harnesses that weren't being reflected in the docs.

Fixes angular#20507.
alexeagle pushed a commit to alexeagle/material2 that referenced this issue Dec 16, 2024
We've recently added more test harnesses that weren't being reflected in the docs.

Fixes angular#20507.
alexeagle pushed a commit to alexeagle/material2 that referenced this issue Dec 18, 2024
We've recently added more test harnesses that weren't being reflected in the docs.

Fixes angular#20507.
josephperrott pushed a commit that referenced this issue Dec 18, 2024
We've recently added more test harnesses that weren't being reflected in the docs.

Fixes #20507.
alexeagle pushed a commit to alexeagle/material2 that referenced this issue Dec 18, 2024
We've recently added more test harnesses that weren't being reflected in the docs.

Fixes angular#20507.
kseamon pushed a commit to kseamon/material2 that referenced this issue Dec 18, 2024
We've recently added more test harnesses that weren't being reflected in the docs.

Fixes angular#20507.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area: material.angular.io docs This issue is related to documentation P2 The issue is important to a large percentage of users, with a workaround
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants