fix: schedule order

[krisantuswanandi]

i think the data provided by the api is sorted by updated_at by default, so currently it's not ordered properly.

this fix added sorting schedules manually based on departs_at.

Summary by CodeRabbit

• Refactor
  • Schedule times are now displayed in chronological order, ensuring a clearer and more intuitive presentation for users.

[coderabbitai]

Walkthrough

The update refactors the schedule handling within the ScheduleLine component by introducing explicit sorting of schedule entries based on departure time, specifically considering only the hours and minutes. Previously, the code displayed a slice of the schedules array without sorting. Now, schedules are sorted by departure time before being sliced and displayed, ensuring that the visible schedules appear in chronological order, regardless of their original order in the data.

Changes

File(s)	Change Summary
src/components/station-item.tsx	Refactored schedule handling to sort schedules by departure time before slicing and displaying them.

Poem

In lines of code, the schedules align,
Sorted by time, now perfectly fine.
Rabbits love order, and so do we—
Departure times flow as clear as can be.
Hop, skip, and jump, through minutes we go,
Chronological journeys, all in a row!
🕰️🐇

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0afbb7c and fa615cf.

📒 Files selected for processing (1)

• src/components/station-item.tsx (2 hunks)

🔇 Additional comments (2)

src/components/station-item.tsx (2)

75-84: Great implementation of chronological sorting for schedules!

The sorting implementation correctly addresses the issue with schedule ordering. It properly extracts hours and minutes from the departure times and sorts them chronologically, which is exactly what was needed according to the PR description.

A couple of suggestions:

1. Consider browser compatibility for the toSorted() method which is relatively new (Chrome 110+, Firefox 115+, Safari 17+). You might want to use [...filteredSchedules].sort() for better compatibility.

2. The comment about "ignoring the date part" is helpful, but you might want to add a brief explanation of why this approach is used (e.g., "We only care about time of day ordering regardless of date").

---

135-135: Correct usage of the sorted schedules array

Good job consistently using the sortedSchedules array here to maintain chronological ordering in the accordion content as well.

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

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)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.