-
Notifications
You must be signed in to change notification settings - Fork 77
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
Next major version #215
Comments
If this is going to have a dependency on material web components it might be nice to try making it an official component. |
@redbmk I also want that but getting a component through would be far more time consuming and even if we push for it from now we may or may not see it live in 6 or more months. I rather see this live than get work hours wasted |
I agree with @redbmk that we should build this as a Material Design Web component. Here's the relevant issues: material-components/material-components-web#55 |
Maybe the first push could be to get it live using material web components as a dependency, then afterwards submit it as a PR to the official team |
this would be a better approach |
Next major step
There are loads of problems with the current version
Solution
I personally prefer to write a new version using the material components as the baseline e.g using the dialog etc. modules. This would mean we can reduce the size footprint and make our component modular and in line with the modern bundlers to make it more efficient to use in any project.
What are your thoughts/suggestions/anything else @redbmk @westy92 @digitalkaoz @ggomagundan @codingfriendsnippets
The text was updated successfully, but these errors were encountered: