Fix inconsistent behaviors with $currentDate type handling in an update command

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Optimization
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Today, $currentDate in update command has several issues:

      1. Passing in 'false' instead of 'true' keeps the type as date. If this is intended, it should be documented.
        1. Should it accept 1 and 0 as boolean? I would argue against that due do the following...
      2. $type field does not take in typeId like how $type query operator does today.
      3. Shapifying $currentDate always results in something like: 
        example: { $type: "date" }, regardless of whether boolean or string is used. If we want to gather more info on cx usage (especially to gather data for point 1), then it should be shapified to be exactly like how the cx uses $currentDate.

            Assignee:
            Unassigned
            Reporter:
            Calvin Nguyen
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: