[Bug] Fixed dynamic filters for start_at and end_at in ListResults API
#1998
+10
−2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
📃 Description
This PR fixes the filtering results on
api/v1/resultsand point where thecreated_atdate filter was not correctly aliased to allow for a range.You can now filter this endpoint using
start_atandend_at, both params are optional and expect a date or datetime.🪵 Changelog
➕ Added
start_atandend_ataliases forcreated_atso results can be correctly filtered by date range.🗑️ Removed
updated_atdate filter, not needed IMO