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

error message is too vague when user has typoed the timestamp #458

Open
ronja-ui opened this issue Jan 8, 2025 · 0 comments
Open

error message is too vague when user has typoed the timestamp #458

ronja-ui opened this issue Jan 8, 2025 · 0 comments

Comments

@ronja-ui
Copy link
Contributor

ronja-ui commented Jan 8, 2025

Description
If a user typoes a timestamp or uses not supported timestamp format in earliest or latest, the error message is way too vague:

java.lang.RuntimeException: TimeQualifier conversion error: <2021-01-08> can't be parsed.

A more descriptive error message would be more beneficial. All the user needs to know is:

  1. They typoed the timestamp or used a wrong format
  2. A hint what formats are accepted

It's easier and quicker to fix the query when the error message offers the correct format right in the UI.

The way to trigger the error message:

%dpl
index=crud earliest=2021-01-08 latest=2021-01-09
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

No branches or pull requests

1 participant