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
Looks like this was lost in translation when porting
rowCount on the ServiceResponse is being set from data.resultObject.length (row count of the currently returned set), when it really should be set off of data.rowCount (total result set of the current query) which matches our C# PagedResult model:
public T ResultObject { get; set; }
public long RowCount { get; set; }
I think this transformation method is used for all list service calls, whether or not the controller is returning paged results. Maybe it would be best to default it to the current calculated value if data.rowCount is null or undefined.
The text was updated successfully, but these errors were encountered:
Might've been some accidental refactoring when I was originally porting it over. I have a fix for it on my fork, I can update or write tests for it and get it up soon 👍
Looks like this was lost in translation when porting
rowCount
on theServiceResponse
is being set fromdata.resultObject.length
(row count of the currently returned set), when it really should be set off ofdata.rowCount
(total result set of the current query) which matches our C#PagedResult
model:https://github.com/AndcultureCode/AndcultureCode.JavaScript.Core/blob/master/src/utilities/service-utils.ts#L138
https://github.com/AndcultureCode/AndcultureCode.CSharp.Core/blob/master/src/AndcultureCode.CSharp.Core/Models/Errors/PagedResult.cs
I think this transformation method is used for all
list
service calls, whether or not the controller is returning paged results. Maybe it would be best to default it to the current calculated value ifdata.rowCount
is null or undefined.The text was updated successfully, but these errors were encountered: