feat: /teams/{id}/evolutions should sort by current_value desc #116
Labels
No Label
ai-changes-requested
ai-failed
ai-merged
ai-pr-opened
ai-reviewed
ai-reviewing
ai-reviewing
ai-working
bug
enhancement
evolution
performance
phase-0
phase-1a
phase-1b
phase-1c
phase-1d
security
tech-debt
todo
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: cal/paper-dynasty-database#116
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description
GET /api/v2/teams/{team_id}/evolutionsreturns results ordered byplayer_id(insertion order). This means/evo statusin Discord shows a wall of T0/value-0 cards at the top instead of the most progressed players.Current Behavior
Results ordered by player_id — unfiltered view starts with unranked zero-progress cards.
Expected
Default sort by
current_tier DESC, current_value DESCso the most evolved players appear first. Optionally support asortquery param for other orderings.Impact
Without this,
/evo statusis unusable without thetier:1filter — users see 10 pages of zeros before reaching any interesting data.Found during
Phase 1 smoke testing (2026-03-19)
PR opened: #120
The fix is a one-line change in
list_team_evolutions— replaced.order_by(EvolutionCardState.player_id)with.order_by(current_tier DESC, current_value DESC). Most-progressed cards will now appear at the top of/evo statuswithout needing any filter. All 117 tests pass.