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.

Sign up for GitHub

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

Jump to bottom

Better feedback on CQP errors in Advanced search #97

Closed
MartinHammarstedt opened this issue Oct 2, 2019 · 1 comment
Closed

Better feedback on CQP errors in Advanced search #97

MartinHammarstedt opened this issue Oct 2, 2019 · 1 comment
Labels
ux "A user interface is like a joke. If you have to explain it, it’s not that good.” – Martin LeBlanc

Comments

@MartinHammarstedt
Copy link
Member

When a user is using the Advanced search and encounter a CQP error due to a malformed query, we should show the error message from the backend and not just a dead bird. Advanced users can probably handle advanced error messages.
@arildm arildm mentioned this issue Dec 4, 2024
Closed
@arildm arildm added the ux "A user interface is like a joke. If you have to explain it, it’s not that good.” – Martin LeBlanc label Dec 4, 2024
@arildm
Copy link
Member

arildm commented Dec 4, 2024

In general, whenever an API call fails, the client code should throw an exception and the view code should catch it and show an error message with response.ERROR.value and other helpful things like contact info.

Related:

@arildm arildm mentioned this issue Jan 13, 2025
Closed
@arildm arildm closed this as completed in 76d78a4 Jan 15, 2025
@arildm arildm mentioned this issue Jan 16, 2025
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
ux "A user interface is like a joke. If you have to explain it, it’s not that good.” – Martin LeBlanc
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@arildm @MartinHammarstedt