[LineDiagram] : Inline Metro Map into Dotcom - #3464
Merged
Merged
Conversation
joshlarson
approved these changes
Sep 1, 2026
…from CSS classes and associated JS
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
2 participants
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.
Scope
Asana Ticket: 🛠️💈 Inline Metro Map into Dotcom
Implementation
Moved the live component over
Moved the JS hook over
Moved the CSS over
Moved the maplibre-gl dependency over
Removed the map from metro
Rational: Anticipating that we will need to update and enhance this map, it was decided that it would be easier to work on as a Dotcom component than as a Metro component.
Thoughts: Should we update our maplibre-gl version?
Screenshots
No visual difference!
How to test
http://localhost:4001/trip-planner - Confirm that the map still works (markers, lines, zoom, pan, rotate)
http://localhost:4001/preview/stop-map - This too why not