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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

馃悰 FIX: error message for countries not found or without cases #51

Merged
merged 1 commit into from
Apr 30, 2020
Merged

馃悰 FIX: error message for countries not found or without cases #51

merged 1 commit into from
Apr 30, 2020

Conversation

Eronmmer
Copy link
Contributor

Error message for countries not found or without cases

Initially, when users input countries that don't exist or without cases, they get an "API down message". But this has been corrected. View screenshots below

Before:
1

After:
2

@ahmadawais
Copy link
Owner

API must have been down when you ran that query. The Before one. Can you share exact command you ran to get that?

@Eronmmer
Copy link
Contributor Author

@ahmadawais the API wasn't down then. I even successfully ran other commands. There was a slight error in the code that handles catching error for countries not found(404 case) and that was what I fixed. Nothing much. The command I ran was corona <random-country-spelled-wrong>

Copy link
Owner

@ahmadawais ahmadawais left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me! 鉁旓笌

@ahmadawais ahmadawais merged commit 8a587a0 into ahmadawais:master Apr 30, 2020
@ahmadawais
Copy link
Owner

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.

None yet

2 participants