Color/disabled mixins removed properties from the api docs
See original GitHub issueBug, feature request, or proposal:
Docs bug
What is the expected behavior?
A component that implements CanDisable or CanColor should still show color
and disabled
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
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Mixins API Endpoint | Adobe Experience Platform
The /mixins endpoint in the Schema Registry API allows you to programmatically manage XDM mixins within your experience application.
Read more >Mixin - 4.8 - Ember API Documentation
The Mixin class allows you to create mixins, whose properties can be added to other classes. For instance,
Read more >Buttons · Bootstrap v5.0
There are three mixins for buttons: button and button outline variant ... color: $disabled-color; background-color: $disabled-background; // Remove CSS ...
Read more >The DOM Mixin API - Marionette.js Documentation
The DOM mixin manages the DOM on behalf of View and CollectionView . It defines the methods that actually attach and remove views...
Read more >Mixins — OctoPrint master documentation
Plugins declare their instances that implement one or multiple mixins using the __plugin_implementation__ control property. OctoPrint's plugin core collects ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@willshowell Yeah that’s the plan. Just wanted to upgrade everything and revisit this afterwards.
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.