Skip to content

Improve GeoFilter input flexibility and warn on unknown Query parameters#54

Open
rafa-guedes wants to merge 4 commits intomainfrom
query-validation
Open

Improve GeoFilter input flexibility and warn on unknown Query parameters#54
rafa-guedes wants to merge 4 commits intomainfrom
query-validation

Conversation

@rafa-guedes
Copy link
Contributor

@rafa-guedes rafa-guedes commented Mar 13, 2026

Summary

  • Allow GeoFilter.geom to accept tuples and numpy arrays (in addition to lists) for bbox input, coercing to list to avoid serialization issues
  • Warn users when an unknown/misspelled parameter is passed to Query, with a "did you mean?" suggestion for close matches (e.g. tiemfiltertimefilter); unknown params are still silently dropped from serialization, so this is non-breaking
  • Add pytest tests for the new warning behaviour

Test plan

  • pytest tests/test_query.py — all query tests pass
  • pytest tests/test_query.py::test_query_unknown_param_close_match — warns with "did you mean?" for close matches
  • pytest tests/test_query.py::test_query_unknown_param_no_match — warns with "will be ignored" for unrecognised params
  • pytest tests/test_query.py::test_query_valid_params_no_warning — no warning for valid params
  • Full CI suite

🤖 Generated with Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant