Repository navigation
Pair Selection Prototype - #2785
Merged
Merged
Conversation
Member
Author
|
/update-snapshots |
tylercchase
marked this pull request as ready for review
October 8, 2026 15:29
SpicyGarlicAlbacoreRoll
requested changes
Oct 8, 2026
SpicyGarlicAlbacoreRoll
approved these changes
Oct 14, 2026
This branch was successfully deployed
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.
Summary
Base skeleton for pair selection. This only has the logic for loading frames onto the map with the actual request logic waiting for another time.
I've moved the logic for feature loading into its own service that should hopefully be a bit cleaner long term, with the idea being to add more specific logic to that service. The current map service has way too much stuff in it.