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

Improved error message for bad area name #5

Open
ajparsons opened this issue Jan 26, 2023 · 0 comments
Open

Improved error message for bad area name #5

ajparsons opened this issue Jan 26, 2023 · 0 comments
Assignees
Labels
enhancement New feature or request

Comments

@ajparsons
Copy link
Collaborator

Given you know through show_area_values all the valid values, can you throw an error message if an input to subset_coords is outside that?

For instance, if instead of saying 'Croydon' I say 'croydon', the error I get is a 502 error when it actually tries to query the API.

It'd be more helpful if subset_coords told me in advance something like:

'croydon' is not a valid setset, please run 'show_area_values()' for a list of valid areas.

Where this might especially trip people up is if you put multiple areas in, spelt one of them wrong, you would still get data, but might not immediately spot you had less than you wanted.

@CellyRanks CellyRanks added the enhancement New feature or request label Mar 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants