Skip to content

Conversation

@amy-corson-ibigroup
Copy link
Contributor

@amy-corson-ibigroup amy-corson-ibigroup commented Oct 23, 2025

Description:
Fixes a bug where even if a user's location was clearly blocked on mobile, the geolocate button would not reflect that. Now if the app has an existing location error, we will subtly trigger the geolocate button so it updates its UI.

PR Checklist:

  • Does the code follow accessibility standards (WCAG 2.1 AA Compliant)?
  • Are all languages supported (Internationalization/Localization)?
  • Are appropriate Typescript types implemented?

Copy link
Collaborator

@miles-grant-ibigroup miles-grant-ibigroup left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Clever solution! Just a small quick quesiton

const viewedRoute = state.otp?.ui?.viewedRoute?.routeId
const activeNearbyFilters = state.otp?.ui?.nearbyView?.filters
const nearbyFilters = state.otp.config?.nearbyView?.filters
const stops = state.otp.transitIndex.stops
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No more stops?

mapLibreProps={{ reuseMaps: true }}
mapLibreProps={{
onLoad: () => {
return this.setState({ mapLoad: true })
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it be possible to add a comment here that this is about the hack above?

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.

4 participants