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

Datetime filters may be misleading on the "time" part. #435

Open
4 tasks done
robbykrlos opened this issue Feb 21, 2023 · 1 comment
Open
4 tasks done

Datetime filters may be misleading on the "time" part. #435

robbykrlos opened this issue Feb 21, 2023 · 1 comment

Comments

@robbykrlos
Copy link

This is a minor bug.

Prerequisites

  • Are you running the latest version?
  • Are you reporting to the correct repository?
    (enso is made of many specialized packages: https://github.com/laravel-enso)
  • Did you check the documentation?
  • Did you perform a cursory search?

Description

Even though the testing of this issue is not working on 5.0.0 (see #434), the behavior we've seen on 4.9.1 is misleading when it comes to "datetime" filters. Here is why:

If you have a datetime filter Created At, it will ask you only for date. You select 21.02.2023. Your data is having random datetimes like 21.02.2023 10:35:23 ... (with time)

The condition applied in BE is 21.02.2023 00:00:00 == 21.02.2023 10:35:23 which is false. So basically using a datetime filter with value (not interval) is pointless since it will only target entries with time 00:00:00.

Shouldn't time be part of the filter, or when selecting a day, it should cover the whole 24h interval (00:00:00 -> 23:59:59)?

@robbykrlos
Copy link
Author

Any updates?

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