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
When I don't specify sorting in the request, but have defaultSorting set in the Adapter, the response does not contain the meta.sorting object. Therefor my js table does not know the sorting...
Is there any way I can fix it or is it a bug?
The text was updated successfully, but these errors were encountered:
Thank you for your quick reply!
It is not quite what I am looking for.
In my mind, the default sorting should be set on the server an not in JS. Therefor it would be handy if the api attached the sorting object to the meta data.
A workaround like you linked is not quite nice... I think the sorting data is as essential as the pagination data.
Ah I more meant that #225 was about being able to set meta from multiple places - including being able to pass meta out of the adapter (which at the moment is only allowed for pagination).
I totally agree with you, the developer should be able to return meta from the adapter. I think this will be solved when I solve #225 in a future version. At the moment it's not possible so the safest thing for you to do is to always send a sort parameter from the client (Javascript) so that your Javascript always knows what the sort order is.
When I don't specify sorting in the request, but have defaultSorting set in the Adapter, the response does not contain the meta.sorting object. Therefor my js table does not know the sorting...
Is there any way I can fix it or is it a bug?
The text was updated successfully, but these errors were encountered: