Stabilize public exports and typed download boundaries - #96
Open
Claudio9701 wants to merge 1 commit into
Open
Conversation
This was referenced Aug 10, 2026
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.
Stacked on #94.\n\n- replaces fragile wildcard package initializers with explicit supported exports\n- regression-tests the public module surface and internal-name exclusion\n- applies the public Pydantic BoundingBox model to Overpass POI bounds\n- documents coordinate/unit/error conventions and corrects the Nominatim quickstart\n- updates the Pydantic plan to reflect the implemented 0.3 model slice\n\nValidation: 71 tests passed, 4 deselected; Ruff clean; Sphinx -W clean; sdist and wheel build clean.\n\nCloses #95