-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sort feeds from high to low (on the map) #717
Conversation
WalkthroughThe changes in this pull request focus on the Changes
Possibly related PRs
Suggested reviewers
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
🧹 Outside diff range and nitpick comments (2)
ui/src/pages/listen/index.tsx (2)
12-12
: Consider handling loading and error states.The refactoring to store the full query result is good, but we could enhance the user experience by handling loading and error states.
const feedsQueryResult = useFeedsQuery(); + +if (feedsQueryResult.isLoading) { + return <Typography>Loading feeds...</Typography>; +} + +if (feedsQueryResult.error) { + return <Typography color="error">Error loading feeds: {feedsQueryResult.error.message}</Typography>; +}
14-19
: Consider adding type safety to the sort comparison.The sorting implementation is correct, but we can make it more type-safe by ensuring non-null values.
const sortedFeeds = useMemo( () => - feedsQueryResult.data?.feeds.sort((a, b) => b.latLng.lat - a.latLng.lat), + feedsQueryResult.data?.feeds.slice().sort((a, b) => { + if (!a.latLng?.lat || !b.latLng?.lat) return 0; + return b.latLng.lat - a.latLng.lat; + }), [feedsQueryResult.data], );Note: Using
slice()
beforesort()
prevents mutating the original array.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (1)
ui/src/pages/listen/index.tsx
(2 hunks)
🔇 Additional comments (2)
ui/src/pages/listen/index.tsx (2)
4-4
: LGTM!
The useMemo
import is correctly added and necessary for the new sorting implementation.
21-21
: LGTM!
The null check is correctly updated to use the new sortedFeeds
variable.
Summary by CodeRabbit