cube-js/cube

inDateRange with only one date not working as expected

Open

#3,111 opened on Jul 15, 2021

View on GitHubContributor guide
 (4 comments) (1 reaction) (1 assignee)Rust (1,965 forks)batch import
api:resthelp wanted

Repository metrics

Stars
 (19,563 stars)
PR merge metrics
 (PR metrics pending)

Description

Describe the bug As stated in the documentation (operator inDateRange) "If only one date specified the filter would be set exactly to this date". Instead, it seems to consider the only date provided as a lower bound.

To Reproduce

{
  member: "Posts.time",
  operator: "inDateRange",
  values: ['2015-01-01']
}

Expected behavior Same as

{
  member: "Posts.time",
  operator: "inDateRange",
  values: ['2015-01-01', '2015-01-01']
}

or

{
  member: "Posts.time",
  operator: "equals",
  values: ['2015-01-01']
}

Version: 0.26.77

Contributor guide

Research direction
Investigate the inDateRange operator logic in the query parsing/filtering code. Check how single date values are handled and ensure they are treated as an exact date match per documentation.
Tech stack
javascripttypescriptrust
Domain
backendapi
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JavaScriptTypeScriptCube Query Syntax
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70