• add starting guide
• add md documentations of each component

The mixin should push CSS classes depended on set props e.g. secondary-bg

Try to implement this behavior with a vue mixin and pass the style data as object prop.

I accidentally publishd the hole dev directory to npm..

Improvements:

• Merge configs
• Generate static site for github pages
• ...

Following components don't have a documentation yet:

• Tabs
• Textfield
• Theme
• Toolbar
• Typography

Use postcss with serveral plugins.

Mdc-web removed dark-theme support, so a theme component is no longer needed. Instead each component should be customizable.

this mixin should extend the root elements of the components with props e.g. "primary-bg" or "secondary-text"

Use the webpack code splitting feature to load vue components async.

There are a few components in the project that are just wrapping the CSS class of mdc-web and are stateless. As performance optimization we could use functional components that render faster.

Failed to compile with 1 errors
 error  in ./node_modules/material-components-vue/components/Theme/Theme.vue
Module build failed: Error: Couldn't find preset "stage-0" relative to directory "D:\\app\\node_modules\\material-components-vue"

my js:

import MDTheme from 'material-components-vue/components/Theme/Theme.vue'

decouple in sub-components for maximal flexibility (custom theming e.g.)

Simple configurable dark theme integration.

There will be no big umd module with all components in the future. While assembling a PWA app this gives me to much critical blocking CSS. Users who want all components have to import all manually or just that they want.

leave a note to add polyfills if needed

When all components have a demo.

Open a pull request at the material-components-web repository to add this library to the main README.

• webpack 4 x
• babel 7 ×

• snapshot testing the components at a minimum

At the moment it's just possible to use material icons named '_border' as data-off icon.

Refactor the component to use any material icon for data-on and data-off.

Simple configurable RTL integration.

Setters are ill-defined for the LinearProgress component, namely on lines 49 and 52.

We have an attempt to set the value of progress and buffer using function calls, while the setters should be using a normal attribution expression.

Code should be

• this.mdcLinearProgress.progress = this.progress
• this.mdcLinearProgress.buffer = this.buffer

instead of

• this.mdcLinearProgress.progress(this.progress)
• this.mdcLinearProgress.buffer(this.buffer)

This leads to an exception being raised and hinders the functionality of the LinearProgress.

Add secondary theme mixin for relevant components:

• Button
• IconToggle
• Fab
• ...

Without scrollbar the body is not 100% dark.

find a way to use list component instead of duplicate code

e.g. what is the best way to support a fully custimizable button (color, round edges, ...)

...

model should be mdc-web...