fix(database): using empty objects instead of empty arrays for date filtering #198
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.
DateFilter
class was modified to accept an object as a value in addition to string, bool, and array.CompoundFilter
andDateFilter
were updated to use objects instead of empty arrays for thepast_week
,past_month
,past_year
,next_week
,next_month
,next_year
, andthis_week
properties in thedate
array. The tests were also updated to useassertEquals
instead ofassertSame
for the expected and actual arrays.see more: https://developers.notion.com/reference/post-database-query-filter#date