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
This is not a bug, but more like an improvement request.
meter-data/search is used in the UI and in the API and the needs for 2 different channels are different:
UI needs the response entries to be in the order, where the newer ones are first
The API users want to have the order reversed - older ones first.
The problem, the API users have at the moment - they perform the search by filtering by SUCCESS and ERROR status and want to process them by their logical order - older ones first.
At first glance it seems, that maybe the "sort" attribute (asc and desc) would be handy. In that case the different API users can have the data in the order they prefer
The text was updated successfully, but these errors were encountered:
Describe the bug
This is not a bug, but more like an improvement request.
meter-data/search is used in the UI and in the API and the needs for 2 different channels are different:
UI needs the response entries to be in the order, where the newer ones are first
The API users want to have the order reversed - older ones first.
The problem, the API users have at the moment - they perform the search by filtering by SUCCESS and ERROR status and want to process them by their logical order - older ones first.
At first glance it seems, that maybe the "sort" attribute (asc and desc) would be handy. In that case the different API users can have the data in the order they prefer
The text was updated successfully, but these errors were encountered: