Refactor DateFilterDataDto structure or flowNode, instance and variable date filters

XMLWordPrintable

    • Type: Task
    • Resolution: Unresolved
    • Priority: L3 - Default
    • None
    • Affects Version/s: None
    • Component/s: backend

      Context:

      As discussed in a recent Backend Senate, the current DateFilterDataDto structure is not optimal, mainly because we end up with several fields which are unused for most use cases (eg "end" field for rolling and relative filters "include/excludeUndefined" fields for non variable filters). We should improve the existing structure by ensuring we have separate DTOs which include only the fields relevant for their use cases (they will probably still either share a common abstract parent or interface). 

      AT:

      • DateFilterDataDto structure is split to avoid unused fields 

            Assignee:
            Unassigned
            Reporter:
            Helene Waechtler
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: