Skip to content

Fix time parsing for the datasource options #9

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Merged
merged 1 commit into from
Mar 7, 2021

Conversation

ricoberger
Copy link
Member

The user provided time string wasn't parsed correctly. We used the
provided start time also for the end time by mistak. Also the provided
string was always parsed as UTC date instead of the users current
timezone. Both issues are fixed now.

We also added a new input field for the Prometheus resolution. This
option was already present, but the input field was missing. So that a
user wasn't able to change the resolution. The resolution is displayed
in a fourth column in the options modal. This column should also be used
for other datasources (e.g. max results for Jaeger).

The user provided time string wasn't parsed correctly. We used the
provided start time also for the end time by mistak. Also the provided
string was always parsed as UTC date instead of the users current
timezone. Both issues are fixed now.

We also added a new input field for the Prometheus resolution. This
option was already present, but the input field was missing. So that a
user wasn't able to change the resolution. The resolution is displayed
in a fourth column in the options modal. This column should also be used
for other datasources (e.g. max results for Jaeger).
@ricoberger ricoberger merged commit 6f813fc into main Mar 7, 2021
@ricoberger ricoberger deleted the fix-datasource-options branch March 7, 2021 22:42
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant