Make flow node frequency class/string naming consistent

XMLWordPrintable

    • Type: Sub-task
    • Resolution: Done
    • Priority: L3 - Default
    • 3.6.0-alpha2, 3.6.0
    • Affects Version/s: None
    • Component/s: backend
    • None
    • Not defined

      We currently use a mix of, or one of, "frequency" and "count" when describing constants and classes relating to frequency reports. This is kind of redundant and we should instead consistently use one or the other throughout the BE codebase.

        This is the controller panel for Smart Panels app

              Assignee:
              Unassigned
              Reporter:
              Joshua Windels
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: