fix: Better error response for wrong datetime format in REST filter

[gsaivinay]

All Submissions:

• Contributions should target the dev branch. Did you create your branch from dev?
• Have you followed the guidelines in our Contributing document?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?

New Feature Submissions:

1. Does your submission pass tests?
2. Have you formatted your code locally using cargo +nightly fmt --all command prior to submission?
3. Have you checked your code using cargo clippy --all --all-features command?

Changes to Core Features:

• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your core changes, as applicable?
• Have you successfully ran tests with your changes locally?

/claim #3531

[generall]

with if-else statements it will be very easy to forget to implement some parts of the deserializer if we introduce new field here, as compiler won't show any errors

[gsaivinay]

@generall - fair enough, I'll try to change it, do you suggest any approach?

[timvisee]

A match statement with strict enum variants for example. Though to be honest, I don't clearly see how such approach can be used here.

[gsaivinay]

I don't clearly see how such approach can be used here

yes that is true
.

strict enum variants

But isn't that requires introducing a new enum, and we might face the did not match any variant again ?