You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I have a dataGrid with virtualization turned on and using LoadData.
When ever a sort query starts with np() or String(), IQueryable.OrderBy(string) throws an exceptin that the model type does not have the property np or String.
This started with 5.9.5 since you updated to the Linq.Dynmaic V1.6.0. 5.0.0 with the 1.6.0 preview did still work.
Describe the bug
I have a dataGrid with virtualization turned on and using LoadData.
When ever a sort query starts with
np()
orString()
,IQueryable.OrderBy(string)
throws an exceptin that the model type does not have the propertynp
orString
.This started with 5.9.5 since you updated to the Linq.Dynmaic V1.6.0. 5.0.0 with the 1.6.0 preview did still work.
To Reproduce
Steps to reproduce the behavior:
LogData\SmallSession
included in the repositorynp
does not exist in LogItemModel.np(LogEvent.Timestamp) asc
String()
cast.Expected behavior
Data should be ordered and displayed, no exception is thrown.
Desktop (please complete the following information):
Additional context
The
np
istn't even needed here, since the default sort column is never null, not sure why np is used there.The np seems not to be a problem for filtering, only for sorting.
The DataGrid is here: https://github.com/CodeYesterday/Lovi/blob/379f77071b3009ce05d11d6fe2aa72071314a6f7/source/CodeYesterday.Lovi/Components/Pages/LogView.razor#L19
The sorting is applied here: https://github.com/CodeYesterday/Lovi/blob/379f77071b3009ce05d11d6fe2aa72071314a6f7/source/CodeYesterday.Lovi/Session/InMemorySessionDataStorage.cs#L330
The text was updated successfully, but these errors were encountered: