feat(cli): add explicit --descending sort flag#48
Conversation
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
| .maybe_offset(offset) | ||
| .maybe_order(order) | ||
| .ascending(ascending) | ||
| .ascending(if descending { false } else { ascending }) |
There was a problem hiding this comment.
Redundant conditional — descending variable has no effect
Low Severity
The expression if descending { false } else { ascending } is equivalent to just ascending in all valid input states, because the conflicts_with constraint guarantees descending and ascending can never both be true. When descending is true, ascending is already false, so the explicit false branch is redundant. The descending variable appears to influence behavior but never does, which is misleading. This pattern is repeated across all six call sites.


Addresses #17
Summary
--descendingflag as counterpart to existing--ascending.conflicts_with.Notes
Note
Low Risk
Low risk CLI-only change: adds a new
--descendingflag and makes sort-direction flags mutually exclusive without changing default behavior.Overview
Adds an explicit
--descendingCLI flag (mutually exclusive with--ascending) across list-style commands (markets,events,series,sports teams,tags, andcomments).Updates request construction so
--descendingforcesascending=falsewhile preserving the existing default of descending sort when neither flag is provided.Written by Cursor Bugbot for commit 63fa9a1. This will update automatically on new commits. Configure here.