Skip to content

Conversation

RingerJK
Copy link
Contributor

Description

    • Changed experimental extension NavigationRoute#hasUnexpectedClosures -> RouteProgress#hasUnexpectedUpcomingClosures: the algorithm is checking upcoming closures only, ignoring closures where the puck is already at.

cherry-pick #6841

…es` -> `RouteProgress#hasUnexpectedUpcomingClosures` (#6841)

* - Changed experimental extension `NavigationRoute#hasUnexpectedClosures` -> `RouteProgress#hasUnexpectedUpcomingClosures`: the algorithm is checking upcoming closures only, ignoring closures where the puck is already at.
@RingerJK RingerJK self-assigned this Jan 18, 2023
@github-actions
Copy link

Changelog

Features

Bug fixes and improvements

  • Removed NavigationRoute#hasUnexpectedClosures and added RouteProgress#hasUnexpectedUpcomingClosures instead that checks whether route has upcoming unexpected closures (the algorithm does not take into account closures that the puck has already been on) #6841
  • Ensure map-matching considers HOV-only roads as auto accessible. #6834

Known issues ⚠️

Other changes

Android Auto Changelog

Features

Bug fixes and improvements

@RingerJK RingerJK changed the title - Changed experimental extension NavigationRoute#hasUnexpectedClosures -> RouteProgress#hasUnexpectedUpcomingClosures (#6841) cp: Changed experimental extension NavigationRoute#hasUnexpectedClosures -> RouteProgress#hasUnexpectedUpcomingClosures (#6841) Jan 18, 2023
@RingerJK RingerJK merged commit fb1798b into release-v2.10 Jan 18, 2023
@RingerJK RingerJK deleted the cp-kyv-NAVAND-1060-check-upcoming-route-closures branch January 18, 2023 15:05
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.

2 participants