Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Endpoints should support wildcard "*" for geo_values #235

Open
2 tasks
nmdefries opened this issue Jan 8, 2024 · 1 comment
Open
2 tasks

Endpoints should support wildcard "*" for geo_values #235

nmdefries opened this issue Jan 8, 2024 · 1 comment

Comments

@nmdefries
Copy link
Contributor

  • All endpoints should accept wildcard for geo_values
  • All endpoints should use wildcard by default for geo_values

The difficulty with this is that we don't know allowed geos for any (non-covidcast) endpoints. The server side doesn't check geo validity either. We should figure out included geos as part of endpoint documentation upgrades, which will let us explicitly list allowed geos for each endpoint and check user input against that.

@nmdefries nmdefries added this to the Z: epidatr & epidatpy milestone Jan 9, 2024
@nmdefries
Copy link
Contributor Author

This could cause some requests to hit the row limit. Does that need special handling?

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

No branches or pull requests

1 participant