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

Show specific error messages #19

Closed
swapagarwal opened this issue Apr 23, 2016 · 6 comments
Closed

Show specific error messages #19

swapagarwal opened this issue Apr 23, 2016 · 6 comments

Comments

@swapagarwal
Copy link
Owner

Right now, whenever an error occurs, a generic error message (something didn't work as expected) is displayed to the user, who can't determine what went wrong!

@ghost
Copy link

ghost commented May 16, 2016

@swapagarwal Have you got any ideas on how to resolve this? I'm thinking of adding a output['error_msg'] in every module's output variable and have it populated with the equivalent error message within the respective modules itself.

Like say, the query is

define something

I sent and just like #43 it throws an error. So now what I'll do, I'll add an additional entry to output dict as in output['error_msg'] to the corresponding dictionary module with the message like "Sorry sir, I couldn't find it's synonym.\n\n Please ask me something else. " or such similar message.

This would ensure our commitment towards a "beginners entry" code standard with no additional logic to be added into.

Edit: This message would later be shown in the search.py (line 33) of the modules directory instead of the current one.

Let me know if you like it so that I can begin implementing this to all our modules.

@swapagarwal
Copy link
Owner Author

@shanmukhateja It's like you read my mind!
I had exactly this in mind while opening this issue but got busy in other things.
If you like, you may go ahead and implement this (for dictionary module, as a start).
After that, adding to other modules would be low-hanging fruits! 😜

@ghost
Copy link

ghost commented May 17, 2016

Haha so should I PR the dictionary module first? Come on..let me do them all!

@swapagarwal
Copy link
Owner Author

btw, how many modules need this? let's first list them down.

@ghost
Copy link

ghost commented May 17, 2016

I think it's required for all the modules because errors can occur for all modules

@swapagarwal
Copy link
Owner Author

Agreed, except the basic ones like help, request, etc.

edadesd pushed a commit to edadesd/JARVIS-on-Messenger that referenced this issue Jul 12, 2017
# This is the 1st commit message:

Added more tests to test_anime

# This is the commit message swapagarwal#2:

Changed Hummingbird API to Kitsu
# This is the commit message swapagarwal#3:

Added bad query test to test_anime

# This is the commit message swapagarwal#4:

Based slice length on len

# This is the commit message swapagarwal#5:

Removed repeated searches.

# This is the commit message swapagarwal#6:

Broke tests into different functions.

# This is the commit message swapagarwal#7:

Removed whitespace.

# This is the commit message swapagarwal#8:

Added tests based on API response and rating format.

# This is the commit message swapagarwal#9:

Reorganized some calls.

# This is the commit message swapagarwal#10:

Refactored API requests, added tests for rank and episode count

# This is the commit message swapagarwal#11:

Added another test case.

# This is the commit message swapagarwal#12:

Added tests for kitsu and youtube links

# This is the commit message swapagarwal#13:

Stickler corrections.

# This is the commit message swapagarwal#14:

More Stickler corrections.

# This is the commit message swapagarwal#15:

More Stickler corrections.

# This is the commit message swapagarwal#16:

Stickler corrections.

# This is the commit message swapagarwal#17:

Moved declarations closer to point used.

# This is the commit message swapagarwal#18:

Style corrections.

# This is the commit message swapagarwal#19:

Style correction
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant