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

use different color schemes error images #19

Closed
brharrington opened this issue Dec 12, 2014 · 3 comments
Closed

use different color schemes error images #19

brharrington opened this issue Dec 12, 2014 · 3 comments
Assignees
Milestone

Comments

@brharrington
Copy link
Contributor

It has been proposed that the color scheme for the error images could be used to indicate whether it is a user error or some problem with the server.

@brharrington brharrington added this to the backlog milestone Dec 12, 2014
@brharrington brharrington modified the milestones: 1.6.0, backlog May 27, 2017
@svachalek
Copy link
Contributor

Colors would be good, but some clear templating might be more important. Something along the lines of:

There was an internal error in the Atlas server, please report this message to the support team: [internal error message]

or

The load on the Atlas server is currently too high. Please wait a few minutes before resubmitting this query, or contact the support team for further assistance.

or

Query was invalid. Please correct the query and resubmit: [query error message]

or

Your query cannot be processed as written due to the size of the result set. Please consult the FAQ for suggested ways to reduce the size of the result set. [detailed error]

@brharrington
Copy link
Contributor Author

From @nathfisher , add some sort of code that could be used to lookup the error information.

@zimmermatt
Copy link
Contributor

Good suggestions @svachalek and @nathfisher. The color coding change originally conceived for this issue is a relatively quick win, so I've split out the suggestions you made to a separate issue for later implementation.

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

3 participants