bugfix/1675-locations-endpoint-returning-empty-list#1702
Merged
Enovotny merged 4 commits intoApr 23, 2026
Conversation
Enovotny
changed the title
MikeNeilson
approved these changes
Apr 23, 2026
Enovotny
deleted the
bugfix/1675-locations-endpoint-returning-empty-list
branch
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.
The getLocations() method was always returning an empty list when no datum parameter was provided. The code created an empty finalizedResults list and only populated it when datum was not null, then always returned finalizedResults. Instead, return the fetched results directly when datum is null/blank, and only perform datum conversion when necessary.