We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Feature request
Create a custom build of the components which i am interested
Just possible to rely on tree shaking. This does not work properly. Furthermore there is no tree shaking in the css level
Providing a Plunker (or similar) is the best way to get the team to see your issue. Plunker template: https://goo.gl/DlHd6U
I would appreciate if there is a workaround for this.
The text was updated successfully, but these errors were encountered:
Tracked via #4137
As for the CSS, that does capture the per-component styles. For theming, see the theming guide's section on "Theming only certain components"
Sorry, something went wrong.
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.
No branches or pull requests
Bug, feature request, or proposal:
Feature request
What is the expected behavior?
Create a custom build of the components which i am interested
What is the current behavior?
Just possible to rely on tree shaking. This does not work properly. Furthermore there is no tree shaking in the css level
What are the steps to reproduce?
Providing a Plunker (or similar) is the best way to get the team to see your issue.
Plunker template: https://goo.gl/DlHd6U
What is the use-case or motivation for changing an existing behavior?
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Is there anything else we should know?
I would appreciate if there is a workaround for this.
The text was updated successfully, but these errors were encountered: