-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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
Color/disabled mixins removed properties from the api docs #5284
Comments
Yeah this is a known issue. We need to see if we can somehow get a Dgeni processor that properly handles mixins |
@devversion we could alternatively try to pull the properties from the interface (e.g. |
@devversion have you had the chance to look into this? Looking at the dgeni-packages CHANGELOG, it looks like there have been some improvements to how EDIT: I see that #6947 upgrades the version. Maybe something to revisit after that lands. |
@willshowell Yeah that's the plan. Just wanted to upgrade everything and revisit this afterwards. |
* Fixes that properties from mixins (e.g color, disabled) are not showing up in the docs. * No longer runs Dgeni twice when executing the docs task. Fixes angular#5284
* Fixes that properties from mixins (e.g color, disabled) are not showing up in the docs. * No longer runs Dgeni twice when executing the docs task. Fixes #5284
* Fixes that properties from mixins (e.g color, disabled) are not showing up in the docs. * No longer runs Dgeni twice when executing the docs task. Fixes #5284
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Bug, feature request, or proposal:
Docs bug
What is the expected behavior?
A component that implements CanDisable or CanColor should still show
color
anddisabled
as valid properties with descriptions in the component's api reference.Reproduction
Checkbox implements both, but has no reference: https://material.angular.io/components/checkbox/api
The text was updated successfully, but these errors were encountered: