-
Notifications
You must be signed in to change notification settings - Fork 10.1k
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
More InputComponents for common use cases #10529
Comments
Some are straightforward, some are not. Your implementation of InputPassword is simple and clean, but almost identical to the existing InputText. If the existing implementation had a "type"-parameter (enum), making your own wouldn’t be necessary. Same goes for InputDate, a "type"-parameter (datetime, datetime-local etc) would make it more useful. It would be nice and more productive if the basic interaction elements were included. |
Well yes and no. For the functionality I wanted to show you are right, a input type=password would be enough, but my password component has a bit more than just be a password field. I also noticed that I could inherited from InputText and not InputBase<>, but well it is a sample. This is still work in progress and I believe that the guys will add a bit more love to this, meanwhile everyone is free to create their own open source razor component libs and nuget them ;) the purpose of a framework is to provide the foundations to build on top of it. Personally I am loving it! |
Thanks for contacting us. This ask is already covered as part of multiple other issues. So closing this as we will be handling these instead. |
Please add more components in InputComponents for Blazor, covering common tasks like file uploading and select-multiple (perhaps render something like bootstrap-select).
A simple grid and a modal wouldn't hurt either.
And keep up the good work, you are making amazing progress!
The text was updated successfully, but these errors were encountered: