-
Notifications
You must be signed in to change notification settings - Fork 4
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
Add calculated field recorded_end_date to AudioRecording's filter options #261
Comments
👍 - more complicated than I expected but very cool. Cheers. |
😃 yeah, I had to use arel to construct the query. It's like there's a gremlin in the system that sees your issues, and fixes them..... |
Be aware that that dates you send must be in utc, and prefer using |
hmm... that could represent a serious problem. Does this affect all date fields used in all filters? Or just this custom one? |
I think this would affect all date fields in filters (other parts of API should be fine). |
One last question: does it throw an error with bad timezones it fails to parse or does it silently continue? |
I hate to say it, but I think it silently continues with whatever it thought the datetime is 😞 |
This... probably... definitely needs a bit more work... |
It is a separate issue, tracked in #263 |
Request: and calculated field
recorded_end_date
to the filter options in theAudioRecording
model.This field would be defined as:
This field will be useful in completing the saved search story. E.g. find all recordings that have content past a certain date.
The text was updated successfully, but these errors were encountered: