Skip to content

feat: Support intermediate destinations using line topology#2

Draft
google-labs-jules[bot] wants to merge 2 commits intomainfrom
feature/multi-destination-topology-7545709377014784176
Draft

feat: Support intermediate destinations using line topology#2
google-labs-jules[bot] wants to merge 2 commits intomainfrom
feature/multi-destination-topology-7545709377014784176

Conversation

@google-labs-jules
Copy link

This PR introduces support for selecting intermediate stops as destinations (e.g., Vincennes -> Auber) by leveraging the Navitia API to understand line topology.

Changes:

  1. Topology Helper: Added custom_components/idfm/topology.py to fetch and cache route stop sequences.
  2. Config Flow: Modified to list all static stops as potential destinations instead of just dynamic terminuses.
  3. Coordinator: Integrated topology check to filter trains. A train is kept if the configured "Target Stop" is located between the "Start Stop" and the train's "Terminus" in the route sequence.
  4. Sensor: Updated entity naming logic.

This addresses the issue where users could only select final terminuses (e.g., Cergy) even if they alight earlier (e.g., Auber).


PR created automatically by Jules for task 7545709377014784176 started by @azman0101

- Implemented `LineTopology` helper to fetch ordered stop sequences from Navitia API.
- Updated Config Flow to allow selecting any stop as a destination (Target Stop).
- Updated Coordinator to filter trains based on whether they serve the Target Stop (topology check).
- Removed reliance on dynamic destination discovery for initial configuration.
@google-labs-jules
Copy link
Author

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@semanticdiff-com
Copy link

semanticdiff-com bot commented Jan 10, 2026

Review changes with  SemanticDiff

Changed Files
File Status
  custom_components/idfm/config_flow.py  12% smaller
  custom_components/idfm/sensor.py  7% smaller
  custom_components/idfm/__init__.py  1% smaller
  custom_components/idfm/topology.py  0% smaller

- Implemented `LineTopology` helper to fetch ordered stop sequences from Navitia API.
- Updated Config Flow to allow selecting any stop as a destination (Target Stop).
- Updated Coordinator to filter trains based on whether they serve the Target Stop (topology check).
- Removed reliance on dynamic destination discovery for initial configuration.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants