-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Porting to Blazor #4357
Comments
For now, no plans. There is a lot we can improve in Fabric. Better customizability, documentation, testing, and reliability; not to mention a ton more components to solve more challenges! We also want to bring down bundle sizes, and get the issues down to a reasonable number. All of these work items are pretty chunky, and if the core contributors start spending time on porting to a totally different stack, that will take away from those things. So... if there is enough support from the community, both internal and external, to merit switching focus, we would consider that. But right now it's far too early, and there really is so much more to do. |
Closing but will reassess in the future. |
@michaelangotti Any update on this? |
@michaelangotti bump |
+1 for the updating, because of Blazor has become the real project and needs to have a UI with Microsoft standard |
+1 for updating |
To those watching this issue, I wanted to raise awareness that I've opened a new request related to this request since this one had been closed. For reference, the new issue is 10036. |
I know it's still early but I'm curious... Are there any plans to port this project to Blazor? If not we could see if people would be interested in the idea. And if so we could we start a separate repo to create the first UI lib in Blazor.
https://github.com/aspnet/Blazor/issues/334
The text was updated successfully, but these errors were encountered: