Skip to content
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 date range operator for due date and follow-up date of tasks #1060

Merged
merged 4 commits into from
Oct 10, 2024

Conversation

S-Tim
Copy link
Contributor

@S-Tim S-Tim commented Oct 10, 2024

A new operator was introduced to allow filtering tasks which have due dates or follow-up dates in a specific range.

task.dueDate[]2024-10-10T08:54:56Z|2024-10-12T08:54:56Z

The syntax used for the range operator is []. To separate the dates the pipe symbol (|) is used.

closes #1059

@S-Tim S-Tim added Type: enhancement New feature or request Prio: Must This feature must be implemented in current milestone. labels Oct 10, 2024
@S-Tim S-Tim added this to the 4.2.2 milestone Oct 10, 2024
@S-Tim S-Tim self-assigned this Oct 10, 2024
@@ -235,7 +249,7 @@ internal fun toCriterion(filter: String): Criterion {

require(filter.isNotBlank()) { "Failed to create criteria from empty filter '$filter'." }

if (!filter.contains(OPERATORS)) {
if (!OPERATORS.any { filter.contains(it) }) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

!set.any { condition } == set.none { condition }

@zambrovski zambrovski merged commit 0269a03 into develop Oct 10, 2024
8 checks passed
@zambrovski zambrovski deleted the feature/1059-date-range-operator branch October 10, 2024 12:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Prio: Must This feature must be implemented in current milestone. Type: enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Die Kombination von > und < Operator liefert unerwartetes Ergebnis beim Filtern
2 participants