peterthorpe81

> The class responsible for returning the name of the property on which the sorting should be applied returns the wrong string value. Instead of returning the value defined by...

> "it's not easy" is a mediocre answer to a bug that can be fixed. We can work around it all day, but it still doesn't work as intended. What's...

I will try to clarify in a different way. You are assuming Property name is the sort value and this is a mistake. It isn't, its the name of the...

No I'm saying you should ideally ignore the PropertyName and pass the SortFunc for each sort definition along with the filter definitions to the server. That will need a serialization...

> I'm not asking for a solution I'm asking for a library fix. We already patched a the problem. The sort by should just take a string and be done...

> This sounds like a nice experiment! I probably need to implement your batching system, which looks great. Im just using a sempahore slim at the moment which seemed to...

> Hi. Excellent work! It seems like a lot of hard work went into this. It already detects the illegal parameters that we have: > > https://github.com/MudBlazor/MudBlazor/blob/24687738e712c2d2a4733d543a3b1ea33d80051a/src/MudBlazor.Docs/Pages/Components/DropZone/Examples/DropZoneItemSelectorOnlyZoneExample.razor#L3 > > >...

> The illegal parameter detection for first-party components is a neat evolution of the current one that throws at runtime. > > I think that detecting possibly bad attributes on...

> Actually, the tests in meziantou's repo don't look complicated at all. Basically he builds a c# source snippet, or (in our case) a razor component and executes the analyzer...

> Hi, sorry for pushing this, but do you have any ETA for when you can look at the testing? We plan to make RC1 soon, and it would be...