refactor(site): remove redundant client-side sorting of app statuses #21102
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
App statuses are now returned from the API sorted by created_at DESC, id DESC (newest first), so we no longer need to perform client-side sorting. Refs #21099
jaaydenh
approved these changes
Dec 4, 2025
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
App statuses are now returned from the API sorted by
created_at DESC, id DESC(newest first), so we no longer need to perform client-side sorting.This simplifies the code by removing the redundant
.sort()call inAppStatuses.tsx.Depends on #21099