feat(api): filter scope lists by region and catalogue membership - #195
Merged
Merged
Conversation
Region-filtered /scopes and /stats/scopes now list manual scopes configured for the region and imported scopes whose MeshMapper catalogue includes the IATA, instead of inferring membership from observed traffic. Filtered /scopes returns string[] like the unfiltered call. Manual scopes now require a region in config.
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
1 participant
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.
Region-filtered scope lists now follow configured regions and MeshMapper catalogue membership instead of observed traffic.
GET /scopes?iatas|region|regionIdreturnsstring[](same shape as the unfiltered call): manual scopes configured for a matching region, plus imported scopes whose current catalogue includes a requested IATA. IATAs without a catalogue source list only manual scopes. Unfiltered/scopesis unchanged.GET /stats/scopesapplies the same rule when filtered; member scopes with no traffic still appear with zero counts.GetScopesByIATAsquery andScopeSummary.Breaking config: every
scopes:entry now needsregion: <slug>matching a configured region, or startup fails. Matching is unchanged; the region only affects listings.