Presently, when retrieving gateway clients and their test data, the data is returned in chronological order from the earliest entries to the latest. This poses an issue for traversing larger datasets because, to get the latest entries, one would have to paginate to the last page or reverse through the data to the last items.
Proposed Behavior
When gateway clients and their associated test data are fetched, they should be returned in reverse chronological order, starting from the latest entry to the earliest entry. This will improve efficiency by allowing users to access the most recent data without needing to paginate through older entries.
Presently, when retrieving gateway clients and their test data, the data is returned in chronological order from the earliest entries to the latest. This poses an issue for traversing larger datasets because, to get the latest entries, one would have to paginate to the last page or reverse through the data to the last items.
Proposed Behavior
When gateway clients and their associated test data are fetched, they should be returned in reverse chronological order, starting from the latest entry to the earliest entry. This will improve efficiency by allowing users to access the most recent data without needing to paginate through older entries.