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
Recent behavior on the deployment versions endpoint appears to return the oldest versions first, and we don't see a way to request newest-first ordering.
That means any client that wants to show the latest versions first now has to:
page through the full result set
fetch all versions client/server-side
sort locally by createdAt desc
optionally trim back down to a safe UI-sized list
It would be helpful if this endpoint supported an explicit sort-order parameter so clients could request the desired ordering directly.
Examples:
sort=createdAt&direction=desc
order=desc
any equivalent API shape that makes newest-first deterministic
Why this would help:
avoids extra pagination work for a very common "show latest versions" use case
reduces payload size and client work
makes UI behavior predictable
avoids every integration having to reimplement the same workaround
If changing the default is undesirable for backwards-compatibility, a parameterized opt-in would still solve the problem cleanly.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Recent behavior on the deployment versions endpoint appears to return the oldest versions first, and we don't see a way to request newest-first ordering.
That means any client that wants to show the latest versions first now has to:
createdAt descIt would be helpful if this endpoint supported an explicit sort-order parameter so clients could request the desired ordering directly.
Examples:
sort=createdAt&direction=descorder=descWhy this would help:
If changing the default is undesirable for backwards-compatibility, a parameterized opt-in would still solve the problem cleanly.
Beta Was this translation helpful? Give feedback.
All reactions