Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
📄 Pull Request Description
Be sure to add in your .env.development
Without the key, changes from this PR will not work.
🧩 What was changed?
This PR adds user-location marking and in-map navigation routing to the map feature.
Main changes:
navigateaction in the facility modal (disabled when routing is not possible (no location or user outside campus bounds).💡 Why was it changed?
The changes address a nice-to-have feature from our MLP.
The previous map allowed users to view facilities but not easily answer:
This change improves UX by:
It was needed now to make the map actionable (not only browseable) and align with core way-finding expectations.
⚙️ How was it implemented?
DirectionsService+DirectionsRendererto calculate and draw walking routes.navigatebutton, now with actual functionality.✅ Checklist