fix: sort ApeX vaults by TVL by default - #1342
Merged
Merged
Conversation
miohtama
force-pushed
the
fix/apex-vault-tvl-default-sort
branch
from
July 29, 2026 12:45
054929c to
9cb41f1
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Why
ApeX vaults do not have enough return history for the normal return-based default sort to produce the most useful ordering. The protocol detail page should match the TVL-sorted URL behaviour by showing the largest ApeX vaults first by default.
Lessons learnt
The ApeX protocol page already overrides the default TVL filter because these vaults can sit below the usual listing threshold. Keeping the sort override on the same route keeps this exception local to ApeX and avoids changing the shared vault table defaults.
Summary