Meinrad Recheis
Meinrad Recheis
@lieszkol The reason why we want to keep as many internals private or internal is because making them protected de-facto makes them public and we can't rename, change or remove...
> I'm not sure if the MudDataGrid is truly ready for prime-time This is of course off-topic, but it is ready and works very well.
You are kicking around a few good ideas. Maybe looking at how other libs solve this problem might give us more insights?
Hi @GrigoreCojusneanu, thanks for tagging us, because we can't read every issue, there are just too many. Do you propose to remove the attribute in general or only for IOS?...
This issue is now organized in our [feature requests project](https://github.com/Garderoben/MudBlazor/projects/11) Note: the issue is closed but that doesn't mean that this won't be implemented. Check the project to see how...
Sounds good. In the future we may also want to auto-generate the documentation of each global variable from xml docs @jperson2000
> Just to confirm: are you looking for something that auto-generates docs for all members of `MudGlobal` Yes. And of course the public nested static classes. > Would it be...
No, this is most certainly not intentional.
It would be the same problem in light mode, right? We know that this is a potential problem but we couldn't come up with a better solution. @Garderoben correct me...