I need is_date_after function

[mueedahmed1]

I want to add is_date_after function in date related fields.

Just for an idea scope, I'm writing the json as well

JSON:

{
  "is_date_after": [
     {
       "add_date": [
         {
           "today": []
         },
         -60,
         "day"
      ]
      },
     {
      "var": "actionCreationTimestamp"
     }
     ]
 },

{
  "is_date_after": [
     {
       "add_date": [
         {
           "var": "abcDate"
         },
         -22,
         "day"
      ]
      },
     {
      "today": []
     }
     ]
 },

[ukrbublik]

What's the difference between is_date_after and > operator which should work for dates?

[mueedahmed1]

@ukrbublik Sorry, I didn't get your question.

[ukrbublik]

Please describe your needs for an is_date_after function.
With current abilities of library of latest version you can use dates and relative dates (with help of RELATIVE_DATE function) in LHS and RHS and compare them with operators like >, <, == etc.

[rajanarahul93]

Hi! I’d be happy to help with this. Based on the discussion, it seems like is_date_after would act as a more semantic or readable alias for comparing date expressions using the > operator, especially in JSON logic. If this function is intended for clarity or DSL abstraction, I can implement it accordingly, reusing the existing comparison logic internally. I’m comfortable working with JSON logic and extending such utilities. Let me know if you'd like me to go ahead with it!

[ukrbublik]

@mueedahmed1 Please describe your needs for an is_date_after function.

[CodeKage25]

I’d love to work on this because adding a date comparison helper like is_date_after will make the query builder much more powerful and flexible. My approach is to extend the existing function registry in react awesome query builder by adding an is_date_after handler that takes two arguments and returns a boolean based on comparing the evaluated dates. I will implement it so that values like add_date today minus 60 days or a var timestamp are correctly parsed using the same moment or dayjs logic already in place. I will add unit tests for both JSON examples you provided and a few extra cases to ensure edge conditions work as expected.