Require explicit fee=no for --free - #7
Merged
Merged
Conversation
Unknown OSM fee tags were passing --free, so most "free" results near Bolzano could still bill. --public had the same unknown-tag leak. Refs #6.
galjos
force-pushed
the
fix/free-filter-unknown-fee
branch
2 times, most recently
from
September 4, 2026 08:14
6ec2881 to
699a56a
Compare
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.
Summary
--freenow keeps only chargers withfee=no; unknown fee no longer passes.--publicnow requires an explicit public/yes/permissive access tag.Test plan
uv run pytest tests/test_chargers.py -qpitstop chargers --near 46.498,11.354 --radius 25 --free --jsonreturns onlyfee: false